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 Fri, Apr 06, 2012 at 09:40:16AM +0200, Ulrich Mueller wrote:
> +To enable parsing of ebuilds for the \t{EAPI} value, the \t{EAPI} assignment statement must adhere
> +to the following syntax: It must consist of the string \t{EAPI}, followed by an equals sign,
> +followed by the \t{EAPI} value, optionally enclosed in single or double quotes. The statement must
> +be on its own line, optionally preceded or followed by whitespace (spaces or tabs), optionally
> +followed by a comment. Thus, the line must match the following regular expression:
> +\begin{verbatim}
> +^[ \t]*EAPI=(['"]?)([A-Za-z0-9+_.-]*)\1[ \t]*(#.*)?$
EAPI=
is valid in this. Was that intended?
Will there be any issue overriding EAPI as an env var to call a
function/command?
EAPI=... foo
--
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail : robbat2@g.o
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
|
|
