1 |
On Mon, 09 Mar 2009 14:28:48 -0700 |
2 |
Zac Medico <zmedico@g.o> wrote: |
3 |
> > If we must do that... Can we get something in profiles a bit like |
4 |
> > this: |
5 |
> > |
6 |
> > USE_EXPAND_IMPLICIT="USERLAND KERNEL ELIBC ARCH" |
7 |
> > USE_EXPAND_UNPREFIXED="ARCH" |
8 |
> > USE_EXPAND_VALUES_USERLAND="GNU freebsd" |
9 |
> > USE_EXPAND_VALUES_KERNEL="linux blah" |
10 |
> > USE_EXPAND_VALUES_ELIBC="glibc" |
11 |
> > USE_EXPAND_VALUES_ARCH="x86 amd64 sparc mips blah" |
12 |
> > |
13 |
> > so we've got an enforcable complete list of every legal value for |
14 |
> > them, and less associated mess? |
15 |
> |
16 |
> That seems like a reasonable approach. What about flags that are |
17 |
> commonly forced or masked such as selinux or multilib? Should there |
18 |
> be an implicit exemption for all forced/masked flags, or should we |
19 |
> introduce an IMPLICIT_IUSE profile variable to enumerate specific |
20 |
> ones which are implicit members of IUSE? |
21 |
|
22 |
I'd rather we were explicit about what's implicit. All forced / masked |
23 |
flags is a pretty large set. |
24 |
|
25 |
-- |
26 |
Ciaran McCreesh |