Ciaran McCreesh wrote:
On Fri, 13 Oct 2006 02:40:59 -0700 Zac Medico <[EMAIL PROTECTED]>
wrote:
| At the profile level, I've added support for package.use
| which behaves like /etc/portage/package.use that everyone is familiar
| with. The intention is that the IUSE defaults will be used for
| default flags that should be enabled regardless of profile.
Isn't that why we have base profiles? It's kinda icky moving that
metadata partially into ebuilds IMO...
I think for me; it's a matter of duplication.
I can take this ebuild and move it to a different repo; the "sane
defaults" for a particular package move with it.
I do agree that it's a fine line between what belongs in the ebuild
versus profile default USE. I have a feeling that if this is not well
hashed out we will get people setting flags improperly.
Improperly would perhaps be setting QT on at the ebuild level.
Properly may be setting USE=fortran for gcc; perhaps to match the
behavior of upstream at the ebuild level.
--
[email protected] mailing list
