1 |
>>>>> On Sun, 13 May 2012, David Leverton wrote: |
2 |
|
3 |
> The package manager may optionally determine the EAPI of an ebuild by parsing its first non-blank |
4 |
> -and non-comment line, using above regular expression. If a recognised EAPI has been determined |
5 |
> -such, then the package manager must make sure that the \t{EAPI} value obtained by sourcing the |
6 |
> +and non-comment line, using the above regular expression. If it matches, the \t{EAPI} is the |
7 |
> +substring matched by the capturing parentheses (\t{0} if empty), otherwise it is \t{0}. |
8 |
> +The package manager must make sure that the \t{EAPI} value obtained by sourcing the |
9 |
> ebuild with bash is identical to the EAPI obtained by parsing. The ebuild must be treated as |
10 |
> invalid if these values are different. |
11 |
|
12 |
Hm, the condition "If a recognised EAPI has been determined such, |
13 |
then ..." is important and shouldn't be removed. |
14 |
|
15 |
If the result of parsing is an EAPI not known to the package manager, |
16 |
then the ebuild must not be sourced (but be rejected immediately). |
17 |
|
18 |
Ulrich |