| 1 |
On Saturday 23 July 2005 14:34, Alec Warner wrote: |
| 2 |
> In order to receive this helpful data we basically need 4 or 5 things. |
| 3 |
> |
| 4 |
> RESTRICT="Warning" |
| 5 |
> pkg_warn() |
| 6 |
> Features="Warning" |
| 7 |
> PORTAGE_WARNLEVEL={0-5} ( in make.conf ) |
| 8 |
> EBUILD_WARNLEVEL={1-5} ( in the ebuild ) |
| 9 |
> patches to portage |
| 10 |
> Developer awareness and use ( QA++ ). |
| 11 |
|
| 12 |
Too complex. RESTRICT="warn" + pkg_warn() is enough. |
| 13 |
|
| 14 |
> 2. If Features="Warning" is set, pkg_warn() will die pending some |
| 15 |
> action ( to be determined, offhand I'd say put pkg_warn() after |
| 16 |
> src_unpack() and have "emerge --warning-disable CPV" touch |
| 17 |
> $WORKDIR/.warning ) If $WORKDIR/.warning exists then continue the build |
| 18 |
> and assume that the admin has read the content of pkg_warn(). |
| 19 |
|
| 20 |
Why make it so difficult? Why die at all? The point of having pkg_warn() |
| 21 |
separate to pkg_setup() is so that dieing is not necessary and the |
| 22 |
information can be given up front. |
| 23 |
|
| 24 |
`emerge --warnings -uDvp world` could list the warnings after the upgrade |
| 25 |
list for example. FEATURES="warnings" can permanently enable --warnings |
| 26 |
similar to FEATURES="buildpkg" works. |
| 27 |
|
| 28 |
Does this not cover all bases already? |
| 29 |
|
| 30 |
-- |
| 31 |
Jason Stubbs |
Archives