| 1 |
On Fri, 6 Apr 2012 09:40:16 +0200 |
| 2 |
Ulrich Mueller <ulm@g.o> wrote: |
| 3 |
> The plan would be to allow optional parsing now, and make it mandatory |
| 4 |
> in future, when EAPI 5 is introduced (i.e. EAPI 5 aware package |
| 5 |
> managers would have to implement it). |
| 6 |
|
| 7 |
What does this do, if EAPI 5 includes per-package eclasses? |
| 8 |
|
| 9 |
inherit foo |
| 10 |
EAPI=5 |
| 11 |
|
| 12 |
Where 'foo' would be found per-package for EAPI 5, and globally |
| 13 |
otherwise. (This is a general problem, and inherit is just an example, |
| 14 |
so it needs to be addressed even if you say "well we won't allow that". |
| 15 |
The same kind of thing happens if we stick versionator into the package |
| 16 |
mangler, or anything else global scopeish.) |
| 17 |
|
| 18 |
What about this, if the package manager does not support the new |
| 19 |
behaviour yet? |
| 20 |
|
| 21 |
EAPI=5 |
| 22 |
# 20 lines |
| 23 |
EAPI=4 |
| 24 |
|
| 25 |
The proposal as worded doesn't seem to outlaw this, and moving to |
| 26 |
"mandatory for EAPI 5" doesn't help either, since under current rules |
| 27 |
that ebuild isn't EAPI 5. |
| 28 |
|
| 29 |
What about this? |
| 30 |
|
| 31 |
cat <<END |
| 32 |
EAPI=5 |
| 33 |
END >/dev/null |
| 34 |
EAPI=4 |
| 35 |
|
| 36 |
That's also not EAPI 5, so it's not affected by the rules as written. |
| 37 |
|
| 38 |
What about this? |
| 39 |
|
| 40 |
if [[ $EAPI = 5 ]] ; then |
| 41 |
blah |
| 42 |
fi |
| 43 |
|
| 44 |
EAPI=5 |
| 45 |
|
| 46 |
Also relevant: https://bugs.gentoo.org/show_bug.cgi?id=411069 |
| 47 |
|
| 48 |
The solution the Council decided upon doesn't do away with the whole |
| 49 |
"pre-source" vs "post-source" EAPI problem. |
| 50 |
|
| 51 |
-- |
| 52 |
Ciaran McCreesh |
Archives