| 1 |
On Tue, 10 Apr 2012 12:53:27 +0200 |
| 2 |
Ulrich Mueller <ulm@g.o> wrote: |
| 3 |
> +If an ebuild contains an \t{EAPI} assignment, the statement must |
| 4 |
> occur within the first 20 lines. An ebuild must not contain more |
| 5 |
> than one \t{EAPI} assignment. |
| 6 |
|
| 7 |
This still doesn't explain what should happen here: |
| 8 |
|
| 9 |
inherit foo |
| 10 |
EAPI=5 |
| 11 |
|
| 12 |
There are two issues: which EAPI's 'inherit' behaviour is used, and |
| 13 |
what is the value of the $EAPI variable when sourcing foo.eclass? |
| 14 |
Eclasses seem to like doing $EAPI-dependent things... |
| 15 |
|
| 16 |
-- |
| 17 |
Ciaran McCreesh |
Archives