On 23:20 Mon 17 Dec , Piotr Jaroszyński wrote: > Abstract > ======== > > This GLEP proposes usage of EAPI-suffixed file extensions for ebuilds (for > example, foo-1.2.3.ebuild-1). > > Motivation > ========== > > Including EAPI in the ebuild file extension has the following advantages: > > * Possibility to extend the versioning rules in an EAPI, and to use them > immediately in the Gentoo tree. For example, addition of the scm suffix - > GLEP54 [#GLEP54]_. > > * Possibility to extend the behaviour of inherit and add new global scope > functions (as a result of not sourcing ebuilds with unsupported EAPI).
Here's some other ideas for how to express EAPI. What if we: Used EAPI-named subdirectories instead of tagging it into the filename? Used (and required) filesystem extended attributes? Stuck ranges into metadata.xml for which EAPIs applied? Thanks, Donnie -- [EMAIL PROTECTED] mailing list
