On Mon, 09 Mar 2009 14:28:48 -0700
Zac Medico <zmedico@g.o> wrote:
> > If we must do that... Can we get something in profiles a bit like
> > this:
> > 
> >     USE_EXPAND_IMPLICIT="USERLAND KERNEL ELIBC ARCH"
> >     USE_EXPAND_UNPREFIXED="ARCH"
> >     USE_EXPAND_VALUES_USERLAND="GNU freebsd"
> >     USE_EXPAND_VALUES_KERNEL="linux blah"
> >     USE_EXPAND_VALUES_ELIBC="glibc"
> >     USE_EXPAND_VALUES_ARCH="x86 amd64 sparc mips blah"
> > 
> > so we've got an enforcable complete list of every legal value for
> > them, and less associated mess?
> 
> That seems like a reasonable approach. What about flags that are
> commonly forced or masked such as selinux or multilib? Should there
> be an implicit exemption for all forced/masked flags, or should we
> introduce an IMPLICIT_IUSE profile variable to enumerate specific
> ones which are implicit members of IUSE?

I'd rather we were explicit about what's implicit. All forced / masked
flags is a pretty large set.

-- 
Ciaran McCreesh