1 |
On Fri, Apr 6, 2012 at 10:29 AM, Robin H. Johnson <robbat2@g.o>wrote: |
2 |
|
3 |
> On Fri, Apr 06, 2012 at 09:40:16AM +0200, Ulrich Mueller wrote: |
4 |
> > +To enable parsing of ebuilds for the \t{EAPI} value, the \t{EAPI} |
5 |
> assignment statement must adhere |
6 |
> > +to the following syntax: It must consist of the string \t{EAPI}, |
7 |
> followed by an equals sign, |
8 |
> > +followed by the \t{EAPI} value, optionally enclosed in single or double |
9 |
> quotes. The statement must |
10 |
> > +be on its own line, optionally preceded or followed by whitespace |
11 |
> (spaces or tabs), optionally |
12 |
> > +followed by a comment. Thus, the line must match the following regular |
13 |
> expression: |
14 |
> > +\begin{verbatim} |
15 |
> > +^[ \t]*EAPI=(['"]?)([A-Za-z0-9+_.-]*)\1[ \t]*(#.*)?$ |
16 |
> EAPI= |
17 |
> is valid in this. Was that intended? |
18 |
> |
19 |
> Will there be any issue overriding EAPI as an env var to call a |
20 |
> function/command? |
21 |
> EAPI=... foo |
22 |
> |
23 |
|
24 |
That's kind of a no no; specific usage? |
25 |
~harring |