Gentoo Archives: gentoo-pms

From: Ciaran McCreesh <ciaran.mccreesh@××××××××××.com>
To: gentoo-pms@l.g.o
Subject: Re: [gentoo-pms] EAPI specification in ebuilds
Date: Fri, 06 Apr 2012 18:10:56
Message-Id: 20120406190849.136f7bec@googlemail.com
In Reply to: [gentoo-pms] EAPI specification in ebuilds by Ulrich Mueller
On Fri, 6 Apr 2012 09:40:16 +0200
Ulrich Mueller <ulm@g.o> wrote:
> The plan would be to allow optional parsing now, and make it mandatory > in future, when EAPI 5 is introduced (i.e. EAPI 5 aware package > managers would have to implement it).
What does this do, if EAPI 5 includes per-package eclasses? inherit foo EAPI=5 Where 'foo' would be found per-package for EAPI 5, and globally otherwise. (This is a general problem, and inherit is just an example, so it needs to be addressed even if you say "well we won't allow that". The same kind of thing happens if we stick versionator into the package mangler, or anything else global scopeish.) What about this, if the package manager does not support the new behaviour yet? EAPI=5 # 20 lines EAPI=4 The proposal as worded doesn't seem to outlaw this, and moving to "mandatory for EAPI 5" doesn't help either, since under current rules that ebuild isn't EAPI 5. What about this? cat <<END EAPI=5 END >/dev/null EAPI=4 That's also not EAPI 5, so it's not affected by the rules as written. What about this? if [[ $EAPI = 5 ]] ; then blah fi EAPI=5 Also relevant: https://bugs.gentoo.org/show_bug.cgi?id=411069 The solution the Council decided upon doesn't do away with the whole "pre-source" vs "post-source" EAPI problem. -- Ciaran McCreesh

Attachments

File name MIME type
signature.asc application/pgp-signature