| 1 |
Hi there, |
| 2 |
|
| 3 |
a while ago Thilo Bangert spent quite some time on filing lots of bugs. While |
| 4 |
I appreciate such QA efforts I don't agree with those bugs at all. |
| 5 |
|
| 6 |
All of these bugs were for the use of the FEATURES variable in ebuilds, which |
| 7 |
is a very convenient thing to work around issues. |
| 8 |
For example known failures with FEATURE="distcc" or funky things like test |
| 9 |
failures with FEATURES="userpriv" and so on. All other methods of expressing |
| 10 |
that are much more verbose and inherently sucky. |
| 11 |
|
| 12 |
One example of such a bug is https://bugs.gentoo.org/show_bug.cgi?id=278960 |
| 13 |
for those too lazy to search. |
| 14 |
|
| 15 |
To quote: |
| 16 |
"FEATURES is a portage specific package manager configuration variable not |
| 17 |
specified in PMS and cannot reliably be used in ebuilds or eclasses." |
| 18 |
|
| 19 |
Well then, I suggest we finally start documenting reality and fix PMS. The use |
| 20 |
of the FEATURES variable, while it has been there for ... uhm ... as long as I |
| 21 |
can think back, actually :), should not be randomly suppressed. |
| 22 |
|
| 23 |
So ... what's your opinion? Should we do things as they are correct, or as |
| 24 |
they are specified in PMS? ( /me points at bash 3.0 ) |
| 25 |
|
| 26 |
Take care, |
| 27 |
|
| 28 |
Patrick |
Archives