1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Georgi Georgiev wrote: |
5 |
> maillog: 23/07/2005-15:04:06(+0900): Jason Stubbs types |
6 |
> |
7 |
>>On Saturday 23 July 2005 14:34, Alec Warner wrote: |
8 |
>> |
9 |
>>>In order to receive this helpful data we basically need 4 or 5 things. |
10 |
>>> |
11 |
>>>RESTRICT="Warning" |
12 |
>>>pkg_warn() |
13 |
>>>Features="Warning" |
14 |
>>>PORTAGE_WARNLEVEL={0-5} ( in make.conf ) |
15 |
>>>EBUILD_WARNLEVEL={1-5} ( in the ebuild ) |
16 |
>>>patches to portage |
17 |
>>>Developer awareness and use ( QA++ ). |
18 |
>> |
19 |
>>Too complex. RESTRICT="warn" + pkg_warn() is enough. |
20 |
>> |
21 |
>>>2. If Features="Warning" is set, pkg_warn() will die pending some |
22 |
>>>action ( to be determined, offhand I'd say put pkg_warn() after |
23 |
>>>src_unpack() and have "emerge --warning-disable CPV" touch |
24 |
>>>$WORKDIR/.warning ) If $WORKDIR/.warning exists then continue the build |
25 |
>>>and assume that the admin has read the content of pkg_warn(). |
26 |
>> |
27 |
>>Why make it so difficult? Why die at all? The point of having pkg_warn() |
28 |
>>separate to pkg_setup() is so that dieing is not necessary and the |
29 |
>>information can be given up front. |
30 |
>> |
31 |
>>`emerge --warnings -uDvp world` could list the warnings after the upgrade |
32 |
>>list for example. FEATURES="warnings" can permanently enable --warnings |
33 |
>>similar to FEATURES="buildpkg" works. |
34 |
Heh, I was attempting to combine your two suggestions in a good way and |
35 |
failed. This sounds much better ;) |
36 |
|
37 |
>>Does this not cover all bases already? |
38 |
> |
39 |
> |
40 |
> Just to make sure I am not missing something. |
41 |
> |
42 |
> Does this cover the |
43 |
> |
44 |
> - If you are upgrading from a version of udev prior to 046 ... |
45 |
> - If you are upgrading from a version of udev prior to 050 ... |
46 |
> - If you are upgrading from a version of udev prior to 057 ... |
47 |
> - If you are upgrading from a version of udev prior to 059 ... |
48 |
> |
49 |
> cases automatically? I.e. *not* showing irrelevant warnings on every |
50 |
> upgrade/rebuild. |
51 |
> |
52 |
|
53 |
The writer of pkg_warn() could do this, it's still in the ebuild and |
54 |
could use the normal ebuild functions to determine what the user is |
55 |
running ( has_version() and whatnot ) and then run a case statement on that. |
56 |
-----BEGIN PGP SIGNATURE----- |
57 |
Version: GnuPG v1.4.1 (GNU/Linux) |
58 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
59 |
|
60 |
iQIVAwUBQuJZ22zglR5RwbyYAQKoQRAAkvXkNNNBA63jlqhN55v8JfHtcKJ747Qa |
61 |
HsGHYmdVC++tegfPYGYFW5TTHaaGiePYeK2NTqbjODFPpb/uMP4+ZP6XPRT19vNC |
62 |
2ruK4tChPnpsKu9vyKaRFOd/oDOmryuX8zUrzVfBUPr+P5BUuv2fVOZegrqF31ej |
63 |
USO7WFpriEZ6Bv8QEbPQlj/cqyOMKdicFoU/iBSA69cX3ZJfBNbyabkaebaIyxAs |
64 |
c4o3+21hBYfXG/JLPDO9S83xLTQhLWArR2HpeezuWwJMa+IJ5fGtLIN7pmbmuUvN |
65 |
ZYwtl+kWigJEBlD99xGolJ6/aw5cN3A9/FZ2qhH70xfy43KvJA4qHsQld3vr6R/D |
66 |
lBCl1v21sBbKkEUByM3TdcNu9f2EeGeMf+GFRDgZxfADNdCwWjqH7jPhgLwJKpFa |
67 |
s9m+7ZRqrBiANp7M5nvVcD7lYkk5yCpmW3fjo2gsP0oKlXZrV0LXMuChIVscqkzK |
68 |
iol0zs5rU0h7ywcG6FfhzqBUKB8s/hTyV0o/oaD8pxr5Wxkvgzl146MrHsYRvTXG |
69 |
Jngi175osu+BsdrCP+0bbZdXosKGvaDhEBcpqDgIkW2O3iDHJHhf/BFMm2wjZZsy |
70 |
CYSavpVm/p9sWMTiuWCLjxebXLn0xHpXdhKLB0fO1QbdxThn85MTdwptc8PAUcJf |
71 |
u3RczNQLdgE= |
72 |
=TTlc |
73 |
-----END PGP SIGNATURE----- |
74 |
-- |
75 |
gentoo-dev@g.o mailing list |