@@ -341,6 +342,7 @@@@ -421,9 +423,45 @@Extend versioning rules in an EAPI - for example, addition of the scm suffix - GLEP54 [1] or allowing more sensible version formats like 1-rc1, 1-alpha etc. to match upstream more closely. +Use newer bash features.
Not the best error message, especially if there are lots of them.
+|& is a new type of redirection added in bash-4. It cannot be used even in +local scope as bash still parses the whole ebuild.
+sys-apps/foo-1.ebuild:
+
+EAPI="5"
+
+foo() {
+ echo "foo" |& cat
+}
+
+Result:
+
+/var/lib/gentoo/repositories/peper/sys-apps/foo/foo-1.ebuild: line 8: syntax error near unexpected token `&'
+/var/lib/gentoo/repositories/peper/sys-apps/foo/foo-1.ebuild: line 8: ` echo "foo" |& cat'
+*
+* ERROR: sys-apps/foo-1 failed.
+* Call stack:
+* ebuild.sh, line 1879: Called _source_ebuild
+* ebuild.sh, line 1818: Called die
+* The specific snippet of code:
+* source "${EBUILD}" || die "error sourcing ebuild"
+* The die message:
+* error sourcing ebuild
+*
+* If you need support, post the topmost build error, and the call stack if relevant.
+* This ebuild is from an overlay: '/var/lib/gentoo/repositories/peper/'
+* ... done!
+
+!!! All ebuilds that could satisfy "sys-apps/foo" have been masked.
+!!! One of the following masked packages is required to complete your request:
+- sys-apps/foo-1 (masked by: corruption)
+
+Again, not the best error.
+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 @@ -433,7 +471,7 @@ issues listed on the common portage problems page - [2] - 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 @@ -441,7 +479,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. @@ -482,9 +520,9 @@ given system.
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.