Hi,
The only reason I can think of for using no... USE-flags is that the maintainer wants to provide an option for disabling a certain feature, but prefers that it's turned on by default and doesn't like to add an entry to make.defaults in the profile.
Yep, and that's the only problem I see. I don't like the idea of disabling something with enabling a switch. Also, it might be confusing:
[EMAIL PROTECTED] ~ $ USE="*" emerge -pv mozilla
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] net-www/mozilla-1.7.5 +crypt -debug +gnome +java -ldap -mozdevelop +moznomail +moznoxft +mozsvg -mozxmlterm +ssl +xinerama* -xprint 0 kB [1]
I know it's evil to use *, but USE="*" says: use everything, it doesn't say: Don't compile the mozilla mail client. As ciaranm already said, there is no way to force a use flag beeing which would be needed with no-use flags.
The only solution i can see is to put i.e. a flag mozmail into make.defaults, but that's ugly too.
Just my 0.05 SFr.,
blubb
signature.asc
Description: OpenPGP digital signature
