Gentoo Archives: gentoo-pms

From: David Leverton <levertond@××××××××××.com>
To: gentoo-pms@l.g.o
Cc: David Leverton <levertond@××××××××××.com>
Subject: [gentoo-pms] [PATCH 1/2] Clarify wording for EAPI parsing
Date: Sun, 13 May 2012 19:12:51
Message-Id: 1336936300-25655-1-git-send-email-levertond@googlemail.com
In Reply to: Re: [gentoo-pms] EAPI specification in ebuilds by Ulrich Mueller
1 ---
2 ebuild-vars.tex | 5 +++--
3 1 files changed, 3 insertions(+), 2 deletions(-)
4
5 diff --git a/ebuild-vars.tex b/ebuild-vars.tex
6 index f3b72bf..58ca42e 100644
7 --- a/ebuild-vars.tex
8 +++ b/ebuild-vars.tex
9 @@ -133,8 +133,9 @@ the assignment statement must match the following regular expression:
10 \end{verbatim}
11
12 The package manager may optionally determine the EAPI of an ebuild by parsing its first non-blank
13 -and non-comment line, using above regular expression. If a recognised EAPI has been determined
14 -such, then the package manager must make sure that the \t{EAPI} value obtained by sourcing the
15 +and non-comment line, using the above regular expression. If it matches, the \t{EAPI} is the
16 +substring matched by the capturing parentheses (\t{0} if empty), otherwise it is \t{0}.
17 +The package manager must make sure that the \t{EAPI} value obtained by sourcing the
18 ebuild with bash is identical to the EAPI obtained by parsing. The ebuild must be treated as
19 invalid if these values are different.
20
21 --
22 1.7.3.4

Replies

Subject Author
Re: [gentoo-pms] [PATCH 1/2] Clarify wording for EAPI parsing Ulrich Mueller <ulm@g.o>