public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Mueller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/pms:eapi-5 commit in: /
Date: Thu, 17 May 2012 12:02:26 +0000 (UTC)	[thread overview]
Message-ID: <1337250977.91d1e1e39b034bde7e5b981a5616a127135f37fa.ulm@gentoo> (raw)

commit:     91d1e1e39b034bde7e5b981a5616a127135f37fa
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Thu May 10 07:19:08 2012 +0000
Commit:     Ulrich Mueller <ulm <AT> gentoo <DOT> org>
CommitDate: Thu May 17 10:36:17 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=91d1e1e3

Make parsing of the EAPI assignment mandatory.

---
 ebuild-vars.tex |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/ebuild-vars.tex b/ebuild-vars.tex
index f397f0e..a4586bf 100644
--- a/ebuild-vars.tex
+++ b/ebuild-vars.tex
@@ -136,8 +136,8 @@ the assignment statement must match the following regular expression:
 ^[ \t]*EAPI=(['"]?)([A-Za-z0-9+_.-]*)\1[ \t]*([ \t]#.*)?$
 \end{verbatim}
 
-The package manager may optionally determine the EAPI of an ebuild by parsing its first non-blank
-and non-comment line, using the above regular expression. If it matches, the EAPI is the substring
+The package manager must determine the EAPI of an ebuild by parsing its first non-blank and
+non-comment line, using the above regular expression. If it matches, the EAPI is the substring
 matched by the capturing parentheses (\t{0} if empty), otherwise it is \t{0}. For a recognised
 EAPI, the package manager must make sure that the \t{EAPI} value obtained by sourcing the ebuild
 with bash is identical to the EAPI obtained by parsing. The ebuild must be treated as invalid if



             reply	other threads:[~2012-05-17 12:03 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 12:02 Ulrich Mueller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-09-11 20:41 [gentoo-commits] proj/pms:eapi-5 commit in: / Ulrich Mueller
2012-09-11 20:41 Ulrich Mueller
2012-09-09 19:54 Ulrich Mueller
2012-09-04  8:58 Ulrich Mueller
2012-08-31 16:16 Ulrich Mueller
2012-08-30 19:50 Ulrich Mueller
2012-08-30 18:20 Ulrich Mueller
2012-08-29 12:03 Ulrich Mueller
2012-08-29 12:03 Ulrich Mueller
2012-08-17  6:46 Ulrich Mueller
2012-08-16 19:51 Ulrich Mueller
2012-08-14  5:56 Ulrich Mueller
2012-08-12 12:11 Ulrich Mueller
2012-08-12 12:11 Ulrich Mueller
2012-08-12 12:11 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 12:02 Ulrich Mueller
2012-05-17 10:13 Ulrich Mueller
2012-05-13  7:48 Ulrich Mueller
2012-05-13  7:30 Ulrich Mueller
2012-05-10  7:20 Ulrich Mueller
2012-05-10  7:17 Ulrich Mueller
2012-05-10  7:17 Ulrich Mueller
2012-05-10  7:00 Ulrich Mueller
2012-05-08 20:09 Ulrich Mueller
2012-05-07 13:27 Ciaran McCreesh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1337250977.91d1e1e39b034bde7e5b981a5616a127135f37fa.ulm@gentoo \
    --to=ulm@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox