1 |
On Tue, 10 Apr 2012 23:19:18 +0200 |
2 |
Ulrich Mueller <ulm@g.o> wrote: |
3 |
> Agreed, that would be best. Now we only need a wording for "before |
4 |
> anything else" or "at the top of the ebuild" that is suitable for the |
5 |
> spec. ;-) |
6 |
|
7 |
If the EAPI is to be specified, it must be assigned to precisely once. |
8 |
The assignment must occur within the first 20 lines of the ebuild, must |
9 |
not be preceded by any lines other than blank lines or those that start |
10 |
with optional whitespace followed by a # character, and the assignment |
11 |
statement must match the following regular expression: |
12 |
|
13 |
If EAPI is not specified in this way, the EAPI environment variable may |
14 |
be either empty or set to the value "0". |
15 |
|
16 |
> And if possible, it should be specified in a way that doesn't |
17 |
> invalidate ebuilds with harmless permutations like this: |
18 |
> |
19 |
> WANT_AUTOCONF="2.1" |
20 |
> EAPI="3" |
21 |
|
22 |
That would make it an utter pain in the ass to specify and verify... |
23 |
How much does this right now? |
24 |
|
25 |
-- |
26 |
Ciaran McCreesh |