On 2007/07/10, Mike Frysinger <[EMAIL PROTECTED]> wrote: > for some flags yes ... for others, i dislike that idea for the exact > same reason for the other profile-based suggestions: these defaults > should live in the ebuild, not the profile
I agree that putting per-package defaults in ebuilds is far more elegant than putting them in profiles. My point is just that it doesn't work that well with the USE_ORDER that have been chosen. Even keeping the "-* in make.conf" case appart (obviously my opinion on how it should behave was not widely shared, i can live with that), there is still a problem with -* in make.defaults files: the day you switch from IUSE="nocxx" to IUSE="+cxx", will you remember that, as a consequence, you have to fix hardened/2.6/minimal profile? And also, in bug #61732 there is this comment from Zac about "-foo" not being supported because pkginternal is at the bottom of the stack. Imho, that's missing a great opportunity to make users' life a bit easier... Take the "gtk" flag, which is on by default in usual desktop profiles, but as the drawback to trigger GTK+-1.2 installation just for a few CLI programs which comes with an optional obsolete GUI: wouldn't it be nice if said packages could state IUSE="-gtk", so that the default behavior would be to install only GTK+-2.x GUIs? I'm pretty sure it would save a tenth of /etc/portage/package.use entries for many users. -- TGL. -- [EMAIL PROTECTED] mailing list
