-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
This is a revised version of the profile EAPI lables proposal which
has been discussed previously [1].
Please consider a new 'eapi' profile configuration file that will
designate the EAPI to which any package atoms within the files of a
On Fri, 03 Oct 2008 17:09:43 -0700
Zac Medico [EMAIL PROTECTED] wrote:
In order to allow mixed EAPIs in the profiles, and to avoid having
to configure the EAPI in every single layer, each directory of the
profile stack should be able to either override or inherit the EAPI
value that may have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
On Fri, 03 Oct 2008 17:09:43 -0700
Zac Medico [EMAIL PROTECTED] wrote:
In order to allow mixed EAPIs in the profiles, and to avoid having
to configure the EAPI in every single layer, each directory of the
profile stack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
Please consider a new eapi profile configuration file that will
designate the EAPI to which any package atoms within a given layer
of the profile stack must conform. This will allow package managers
to bail out with an informative error
