On Tuesday 09 December 2003 09:11, John Nilsson wrote:
> What about USE-flags that change dependencies and those that don't.
> Flags that just relates to one package (ex. moznomail) and flags that
> relates to system functionality (ex. nls, pam). Flags that depends on
> other flags. The whole system probably needs to be redesigned.

Sure, change is a negative. But it's a positive as well.

> I think that the settings in make.conf should only be those that
> relates to the whole system. All flags that relates to just one ebuild
> or, like java, have diffrent meanings for all ebuild should be removed
> from make.conf.

You've just said something to the effect of "no local flags in make.conf. some 
global flags are no good either." How is one meant to know which global flags 
are goodies and which are baddies? All local use flags shouldn't hurt by 
being in make.conf, btw. My point is simply that use flags should have a 
clear definition.

Regards,
Jason Stubbs

--
[EMAIL PROTECTED] mailing list

Reply via email to