-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Levi Ramsey wrote:

>
> The main problems at the moment involve broken rpm autogenerated
> dependencies.  To be completely honest, I think that auto-deps are a bad
> idea; the situation wasn't that bad before, right now it's worse, and I
> don't think I see an improvement on that front on the horizon (the fact
> that the perl checker still generates bogus dependencies like perl(the)
> because one of the source files has a comment like "use the Foo widget
> to..." makes this point abundantly clear).  At the very least, auto-deps
> should be removed until right after 9.2 is released and then brought
> back when there's enough time to get them reasonably working.

You're going to have to be more specific. Which auto-generated deps?
library deps (which have been in place for a long time, was it 9.0?),
devel deps (which seem to be ok now), perl deps (which we inherited from
Redhat who had them for RH 9 I think) or the new epoch stuff (which
actually seems to be causing more problems and is due to rpm 4.2)?

The perl dep regex *must* be fixed, it should at least look for a
trailing ";", but I don't see any other non-standard cooker problems.

Regards,
Buchan

- --
|--------------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/J7+ZrJK6UGDSBKcRAgKVAKCAhXh2OKP9eWnbiHqIKwHTPorAVACfckKf
Tts3iyeB7MF6qspy3u3rCFo=
=RiQM
-----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.
******************************************************************

Reply via email to