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
<br><br><div class="gmail_quote">On Fri, Apr 6, 2012 at 10:29 AM, Robin H. Johnson <span dir="ltr"><<a href="mailto:robbat2@g.o">robbat2@g.o</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Fri, Apr 06, 2012 at 09:40:16AM +0200, Ulrich Mueller wrote:<br>
> +To enable parsing of ebuilds for the \t{EAPI} value, the \t{EAPI} assignment statement must adhere<br>
> +to the following syntax: It must consist of the string \t{EAPI}, followed by an equals sign,<br>
> +followed by the \t{EAPI} value, optionally enclosed in single or double quotes. The statement must<br>
> +be on its own line, optionally preceded or followed by whitespace (spaces or tabs), optionally<br>
> +followed by a comment. Thus, the line must match the following regular expression:<br>
> +\begin{verbatim}<br>
> +^[ \t]*EAPI=(['"]?)([A-Za-z0-9+_.-]*)\1[ \t]*(#.*)?$<br>
</div>EAPI=<br>
is valid in this. Was that intended?<br>
<br>
Will there be any issue overriding EAPI as an env var to call a<br>
function/command?<br>
EAPI=... foo<br></blockquote><div><br></div><div>That's kind of a no no; specific usage?</div><div>~harring</div></div>
|
|
