1 |
maillog: 23/07/2005-15:04:06(+0900): Jason Stubbs types |
2 |
> On Saturday 23 July 2005 14:34, Alec Warner wrote: |
3 |
> > In order to receive this helpful data we basically need 4 or 5 things. |
4 |
> > |
5 |
> > RESTRICT="Warning" |
6 |
> > pkg_warn() |
7 |
> > Features="Warning" |
8 |
> > PORTAGE_WARNLEVEL={0-5} ( in make.conf ) |
9 |
> > EBUILD_WARNLEVEL={1-5} ( in the ebuild ) |
10 |
> > patches to portage |
11 |
> > Developer awareness and use ( QA++ ). |
12 |
> |
13 |
> Too complex. RESTRICT="warn" + pkg_warn() is enough. |
14 |
> |
15 |
> > 2. If Features="Warning" is set, pkg_warn() will die pending some |
16 |
> > action ( to be determined, offhand I'd say put pkg_warn() after |
17 |
> > src_unpack() and have "emerge --warning-disable CPV" touch |
18 |
> > $WORKDIR/.warning ) If $WORKDIR/.warning exists then continue the build |
19 |
> > and assume that the admin has read the content of pkg_warn(). |
20 |
> |
21 |
> Why make it so difficult? Why die at all? The point of having pkg_warn() |
22 |
> separate to pkg_setup() is so that dieing is not necessary and the |
23 |
> information can be given up front. |
24 |
> |
25 |
> `emerge --warnings -uDvp world` could list the warnings after the upgrade |
26 |
> list for example. FEATURES="warnings" can permanently enable --warnings |
27 |
> similar to FEATURES="buildpkg" works. |
28 |
> |
29 |
> Does this not cover all bases already? |
30 |
|
31 |
Just to make sure I am not missing something. |
32 |
|
33 |
Does this cover the |
34 |
|
35 |
- If you are upgrading from a version of udev prior to 046 ... |
36 |
- If you are upgrading from a version of udev prior to 050 ... |
37 |
- If you are upgrading from a version of udev prior to 057 ... |
38 |
- If you are upgrading from a version of udev prior to 059 ... |
39 |
|
40 |
cases automatically? I.e. *not* showing irrelevant warnings on every |
41 |
upgrade/rebuild. |
42 |
|
43 |
-- |
44 |
\/ Georgi Georgiev \/ Are we THERE yet? \/ |
45 |
/\ chutz@×××.net /\ /\ |
46 |
\/ +81(90)2877-8845 \/ \/ |