| 1 |
On Sun, 20 Nov 2005 23:23:19 +0100 |
| 2 |
"Spider (D.m.D. Lj.)" <spider@g.o> wrote: |
| 3 |
|
| 4 |
> On Sun, 2005-11-20 at 11:55 -0800, Michael Marineau wrote: |
| 5 |
> |
| 6 |
> > For users who do like the functionality just properly document |
| 7 |
> > the existance of USE_ORDER in the install guide. |
| 8 |
> |
| 9 |
> However, I'd -also- want the IUSE="+auto -bongodrums alpha beta |
| 10 |
> +zeta" to be set, perhaps with a new USE_ORDER variable |
| 11 |
> ":ebuild:" ? |
| 12 |
|
| 13 |
Imho, that's the problem with documenting USE_ORDER (although |
| 14 |
it's a minor one): if a user set USE_ORDER="env:pkg:conf:defaults" |
| 15 |
in his make.conf and a later version of portage introduces some new |
| 16 |
interesting value, he will miss this new feature without noticing. |
| 17 |
|
| 18 |
Since it seems that the common usage of user-defined USE_ORDER is |
| 19 |
to remove values, but not actually to change their priorities |
| 20 |
(probably because the default ones are the only ones which really |
| 21 |
make sense), i would rather see a split in two distinct vars: |
| 22 |
- FOO (i'm not good to invent names) would be portage internal |
| 23 |
and define valid values and their respective priorities. |
| 24 |
- BAR would be accessible to the users as an incremental var, and |
| 25 |
would define what values should be taken into account. |
| 26 |
|
| 27 |
FOO default would be "env:pkg:conf:auto:defaults". |
| 28 |
BAR default would be "auto conf default env pkg". |
| 29 |
|
| 30 |
This way, users could set BAR="-auto" in make.conf, which would |
| 31 |
really mean "take all of the default USE_ORDER but the auto thing". |
| 32 |
And the day "ebuild" or any other new feature is implemented, this |
| 33 |
user will have it automatically (just like he would get any new |
| 34 |
enabled-by-default FEATURES flag for instance). |
| 35 |
|
| 36 |
-- |
| 37 |
TGL. |
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives