1 |
On Sun, 2005-11-20 at 11:55 -0800, Michael Marineau wrote: |
2 |
|
3 |
> However changing this will also lead to many supprises and tick off many |
4 |
> users who don't know why a bunch of flags just vanished. How about we |
5 |
> leave the feature in portage but remove auto from USE_ORDER in the |
6 |
> 2006.0 profile and put a note about the changed behaviour the release |
7 |
> announcements. For users who do like the functionality just properly |
8 |
> document the existance of USE_ORDER in the install guide. |
9 |
|
10 |
*applauds* |
11 |
|
12 |
Sensibility as well as an un-breaking upgrade path! Finally we see |
13 |
thought in this area ; ) |
14 |
|
15 |
Documenting this would be great. However, I'd -also- want the |
16 |
IUSE="+auto -bongodrums alpha beta +zeta" to be set, perhaps with a new |
17 |
USE_ORDER variable ":ebuild:" ? |
18 |
|
19 |
|
20 |
The dark magic was a very good and usable approach, however with the |
21 |
growth of our tree, it has seen its use and it may well be time to phase |
22 |
it out in favour of a more fine-grained mechanism. |
23 |
|
24 |
Adding and documenting a "recommended enable" set, would be a great |
25 |
start. It could also be used to fine-tune packages for the GRP set, in |
26 |
order to do partial on/off settings based on the parts that the |
27 |
maintainers consider "good and reasonable" |
28 |
|
29 |
I know one place where I'd love to see this is fex. the various |
30 |
multimedia backends, openssl/gnutls among other such settings. |
31 |
|
32 |
|
33 |
|
34 |
//Spider |
35 |
|
36 |
|
37 |
-- |
38 |
begin .signature |
39 |
Tortured users / Laughing in pain |
40 |
See Microsoft KB Article Q265230 for more information. |
41 |
end |