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. Does this not cover all bases already? -- Jason Stubbs
pgpRAiy0wX3qU.pgp
Description: PGP signature
