Mike Frysinger wrote:
> On Friday 21 October 2005 05:56 am, Marius Mauch wrote:
> 
>>Petteri Räty wrote:
>>
>>>Every once in a while I see people wanting to use nosomething use flags.
>>>Why don't we have a package.use like we already have a package.mask
>>>file? This would make it possible for developers to turn on use flags by
>>>default in a way that would not cruft the base profiles for every local
>>>use flag.
>>
>>The main problem I'd have with this is the stacking order, e.g.
>>profiles/package.use has "app-misc/foo bar" and make.conf has
>>"USE=-bar", which one should be preferred?
> 
> 
> this is a no brainer
> 
> profile use.defaults
> profile package.use
> profile make.defaults
> user make.conf
> user package.use
> user env
> -mike
> 

I think profile package.use should come after make.defaults. After all
package.use is package specific while make.defauls being generic. Of
course it should not matter if we make it a policy that people can't
turn off global use flags that are on by default on a per package basis,
but I would like this possibility. For example there is the python use
flag which is not needed with every package but there are packages that
need the python use flag for some dependencies. Maybe this was not the
best example but hopefully got the idea across. Of course this will be
fixed when the new portage will come this way some day.

Regads,
Petteri