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

Georgi Georgiev wrote:
> maillog: 23/07/2005-15:04:06(+0900): Jason Stubbs types
> 
>>On Saturday 23 July 2005 14:34, Alec Warner wrote:
>>
>>>In order to receive this helpful data we basically need 4 or 5 things.
>>>
>>>RESTRICT="Warning"
>>>pkg_warn()
>>>Features="Warning"
>>>PORTAGE_WARNLEVEL={0-5} ( in make.conf )
>>>EBUILD_WARNLEVEL={1-5} ( in the ebuild )
>>>patches to portage
>>>Developer awareness and use ( QA++ ).
>>
>>Too complex. RESTRICT="warn" + pkg_warn() is enough.
>>
>>>2.  If Features="Warning" is set, pkg_warn() will die pending some
>>>action ( to be determined, offhand I'd say put pkg_warn() after
>>>src_unpack() and have "emerge --warning-disable CPV" touch
>>>$WORKDIR/.warning )  If $WORKDIR/.warning exists then continue the build
>>>and assume that the admin has read the content of pkg_warn().
>>
>>Why make it so difficult? Why die at all? The point of having pkg_warn()
>>separate to pkg_setup() is so that dieing is not necessary and the
>>information can be given up front.
>>
>>`emerge --warnings -uDvp world` could list the warnings after the upgrade
>>list for example. FEATURES="warnings" can permanently enable --warnings
>>similar to FEATURES="buildpkg" works.
Heh, I was attempting to combine your two suggestions in a good way and
failed.  This sounds much better ;)

>>Does this not cover all bases already?
> 
> 
> Just to make sure I am not missing something.
> 
> Does this cover the
> 
> - If you are upgrading from a version of udev prior to 046 ...
> - If you are upgrading from a version of udev prior to 050 ...
> - If you are upgrading from a version of udev prior to 057 ...
> - If you are upgrading from a version of udev prior to 059 ...
> 
> cases automatically? I.e. *not* showing irrelevant warnings on every
> upgrade/rebuild.
> 

The writer of pkg_warn() could do this, it's still in the ebuild and
could use the normal ebuild functions to determine what the user is
running ( has_version() and whatnot ) and then run a case statement on that.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQuJZ22zglR5RwbyYAQKoQRAAkvXkNNNBA63jlqhN55v8JfHtcKJ747Qa
HsGHYmdVC++tegfPYGYFW5TTHaaGiePYeK2NTqbjODFPpb/uMP4+ZP6XPRT19vNC
2ruK4tChPnpsKu9vyKaRFOd/oDOmryuX8zUrzVfBUPr+P5BUuv2fVOZegrqF31ej
USO7WFpriEZ6Bv8QEbPQlj/cqyOMKdicFoU/iBSA69cX3ZJfBNbyabkaebaIyxAs
c4o3+21hBYfXG/JLPDO9S83xLTQhLWArR2HpeezuWwJMa+IJ5fGtLIN7pmbmuUvN
ZYwtl+kWigJEBlD99xGolJ6/aw5cN3A9/FZ2qhH70xfy43KvJA4qHsQld3vr6R/D
lBCl1v21sBbKkEUByM3TdcNu9f2EeGeMf+GFRDgZxfADNdCwWjqH7jPhgLwJKpFa
s9m+7ZRqrBiANp7M5nvVcD7lYkk5yCpmW3fjo2gsP0oKlXZrV0LXMuChIVscqkzK
iol0zs5rU0h7ywcG6FfhzqBUKB8s/hTyV0o/oaD8pxr5Wxkvgzl146MrHsYRvTXG
Jngi175osu+BsdrCP+0bbZdXosKGvaDhEBcpqDgIkW2O3iDHJHhf/BFMm2wjZZsy
CYSavpVm/p9sWMTiuWCLjxebXLn0xHpXdhKLB0fO1QbdxThn85MTdwptc8PAUcJf
u3RczNQLdgE=
=TTlc
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Reply via email to