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