Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
>>>>> On Sun, 13 May 2012, David Leverton wrote:
> The package manager may optionally determine the EAPI of an ebuild by parsing its first non-blank
> -and non-comment line, using above regular expression. If a recognised EAPI has been determined
> -such, then the package manager must make sure that the \t{EAPI} value obtained by sourcing the
> +and non-comment line, using the above regular expression. If it matches, the \t{EAPI} is the
> +substring matched by the capturing parentheses (\t{0} if empty), otherwise it is \t{0}.
> +The package manager must make sure that the \t{EAPI} value obtained by sourcing the
> ebuild with bash is identical to the EAPI obtained by parsing. The ebuild must be treated as
> invalid if these values are different.
Hm, the condition "If a recognised EAPI has been determined such,
then ..." is important and shouldn't be removed.
If the result of parsing is an EAPI not known to the package manager,
then the ebuild must not be sourced (but be rejected immediately).
Ulrich
|
|
