--- xml/htdocs/proj/en/glep/glep-0055.html 2010/04/07 22:12:52 1.6 +++ xml/htdocs/proj/en/glep/glep-0055.html 2012/05/09 19:37:01 1.7 @@ -4,7 +4,7 @@- +
@@ -79,13 +80,19 @@ sobers us again."+
—Alexander Pope, An Essay on Criticism
This GLEP was voted down by the Council in its meeting on 2010-08-23. +The Council rejected it again in its meeting on 2012-05-08, in favour +of parsing the EAPI from the bash assignment statement in ebuilds.+
This GLEP proposes usage of EAPI-suffixed file extensions for ebuilds (for example, foo-1.2.3.ebuild-1).
The current way of specifying the EAPI in ebuilds is flawed. In order to get the EAPI the package manager needs to source the ebuild, which itself needs the EAPI in the first place. Otherwise it imposes a serious limitation, namely every ebuild, @@ -104,11 +111,11 @@
Following subsections show what happens if you introduce any of the mentioned changes in an ebuild and try to install it with portage 22.214.171.124.
EAPI="5" @@ -146,7 +153,7 @@ - might be pretty confusing to users.
EAPI="5" @@ -171,7 +178,7 @@
Not that bad as user is advised to upgrade portage.
Invalid ebuild name: /var/lib/gentoo/repositories/peper/sys-apps/foo/foo-2-rc1.ebuild @@ -181,7 +188,7 @@
Not the best error message, especially if there are lots of them.
A solution to this problem has to lift those limitations and the only way to do it is to make the EAPI of an ebuild available to the package managers in a way that doesn't require them to source the ebuild. Another important requirement is @@ -228,7 +235,7 @@ issues listed on the common portage problems page -  - show.
The proposed solution is to use EAPI-suffixed file extensions for ebuilds. This allows package managers to trivially read the EAPI from the ebuild filename. It is also backwards compatible, because currently ebuilds are recognised by the @@ -236,7 +243,7 @@ the package managers.
Ebuild filename extension syntax: ebuild[-<EAPI>], where  denotes an optional part, and <EAPI> is the EAPI of the ebuild.
The EAPI used by the ebuild is the EAPI included in the filename if it is set. @@ -281,9 +288,9 @@ with EAPI Y.
Some say it is clear and simple, others that it is ugly and unintuitive.
One of the proposed filename formats: <PKG>-<VER>.eapi-<EAPI>.eb
Some say it is better because the extension is static.