Hi Zac, On 10/13/06, Zac Medico <[EMAIL PROTECTED]> wrote:
I've written a patch for portage [1] that implements per-package default USE flags at both the ebuild and profile levels (discussed a couple of months ago [2] on this list). At the ebuild level, default flags are specified in IUSE with a + prefix as described in bug #61732 [3]. 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. Then, package.use will be used for flags that might vary depending on the profile. For example, a server profile might enable server flags and a desktop profile might enable client flags.
:) This is excellent news, both for the PHP Herd (per-package USE flags) and the Seeds project (per-profile USE flags).
Should we include support in portage for one or both types of per-package default USE flags? If support is included for IUSE defaults now, we won't be able to use them in the tree until after a waiting period or an EAPI bump [4].
I can make good use of both, and would really love to see both supported. Best regards, Stu -- [email protected] mailing list
