I would like to suggest improvement in handling of EAPI in profiles:
Some files could optionally end with ":${EAPI}", which would be used to
specify, which EAPI
should be used for parsing of given file. It would concern at least the
following files:
package.mask
package.use
use.force
use.mask
package.use.force
package.use.mask
And maybe also use.unsatisfiable and package.use.unsatisfiable.Examples: profiles/package.mask:5 could be used to mask dependency atoms with "-scm" or "-live" suffix (if EAPI="5" supports this suffix). profiles/base/use.mask:4 could be used to mask USE flags (which use EAPI="4"-specific syntax) on all profiles inheriting from base profile. Without support for EAPI-versioned files, such actions from above examples might require copying of whole tree of profiles, adding eapi file to new profiles etc. eapi files would still be used to specify EAPI for EAPI-unversioned files in given profiles. -- Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
