-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John Allen wrote:
> On Wednesday 03 September 2003 14:29, G�tz Waschk wrote:
>
>>Am Mittwoch, 3. September 2003, 14:25:18 Uhr MET, schrieb John Allen:
>>
>>>>Check some .spec files for the line like this:
>>>>%define buildfor_mdk90 %(awk '{print ($4 == "9.0")}'
>>>>%{_sysconfdir}/mandrake-release)
>>>
>>>This is really crap; I thought that is what the GNU guys developed
>>>autoconf for. Try to figure out what the system supports by testing the
>>>system, bot checking some freaking version number.
>>
>>Feel free to replace this mechanism in my spec files by a better
>>solution, I'll gladly accept patches.
>
> How about
> %define buildfor_mdk90 %(cat /etc/mandrake-release | sed 's|.*release
\([0-9\.]\+\) .*|\1|g' | grep "^9.2")
>
> where /etc/mandrake/release contains
> Mandrake Linux release 9.2.1 (Cooker) for i586
>
But this isn't an improvement, it's just an additional macro (which
still needs some work).
We have %mdkversion now:
[EMAIL PROTECTED] bgmilne]$ cat /etc/mandrake-release
Mandrake Linux release 9.2 (Cooker) for i586
[EMAIL PROTECTED] bgmilne]$ rpm --eval %mdkversion
920
[EMAIL PROTECTED] bgmilne]$ cat /etc/mandrake-release
Mandrake Linux release 9.1 (Bamboo) for i586
[EMAIL PROTECTED] bgmilne]$ rpm --eval %mdkversion
910
But it didn't exist on 9.0:
[EMAIL PROTECTED] bgmilne]# cat /etc/mandrake-release
Mandrake Linux release 9.0 (dolphin) for i586
[EMAIL PROTECTED] bgmilne]# rpm --eval %mdkversion
%mdkversion
So you can't rely on it at present (or you have to backport it to your
spec file like I have done for a few others already).
But it still doesn't change the fact that needlessly adding releases
makes life more difficult.
Making a macro to detect the distro is the trivial part, ensuring the
package builds correclty on all the releases is what takes the time.
So, submit a spec file that makes provision for slightly different
configurations (such as Mandrake 8.1's kernel update had acl support,
but no acl/attr libraries, so maybe 8.1.1 should have acl support but no
nss_wins/winbind support, maybe by 9.2.1 samba3 will be stable, so it
can build as the system samba and we won't need alternatives anymore,
while we still need them on 9.2, but we still want people to be able to
build samba on 9.1 with alternatives if they really want to). Then, you
still need to test all these packages on all the releases (if you even
have enough machines/disk space/buildroots to build them all), and most
likely will need to fix a few things. Also, we have largely ignored
feature conditionals (anitvirus support on samba for example).
Just go count the lines of conditionals in a reasonable spec file
(kernel, gcc, kde, samba), and then consider how much bigger it would be
if we added an extra 2 point releases per current release.
I really don't think it's feasible without substantially more man-hours,
and I am not going to provide the additional man-hours (so here's your
opportunity!).
- --
|--------------Another happy Mandrake Club member--------------|
Buchan Milne Mechanical Engineer, Network Manager
Cellphone * Work +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering http://www.cae.co.za
GPG Key http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/VfV2rJK6UGDSBKcRAkZ5AKC+K7FVjkl9TnmIbO2d7hHdjBWjLwCdGLNP
HVLOAhK6F5GmmYXvG0C+YK0=
=X50k
-----END PGP SIGNATURE-----
*****************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
*****************************************************************
