public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] [PATCH 1/2] Clarify wording for EAPI parsing
Date: Thu, 17 May 2012 12:15:30 +0200	[thread overview]
Message-ID: <20404.53186.682463.406986@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20400.7609.247161.887999@a1i15.kph.uni-mainz.de>

>>>>> On Sun, 13 May 2012, Ulrich Mueller wrote:

>>>>> On Sun, 13 May 2012, David Leverton wrote:
>>> Hm, the condition "If a recognised EAPI has been determined such,
>>> then ..." is important and shouldn't be removed.

>> I took that out because the PM should treat the parsed EAPI as 
>> authoritative whether or not it's recognised...

>>> If the result of parsing is an EAPI not known to the package manager,
>>> then the ebuild must not be sourced (but be rejected immediately).

>> ... which is basically what you're saying here, but maybe you want 
>> explicit wording saying that the sourcing should be skipped in such a case?

> Updated patch is included below, as discussed on IRC.

Committed.

Ulrich



  reply	other threads:[~2012-05-17 10:15 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06  7:40 [gentoo-pms] EAPI specification in ebuilds Ulrich Mueller
2012-04-06 17:29 ` Robin H. Johnson
2012-04-06 17:32   ` Brian Harring
2012-04-06 17:33   ` Ciaran McCreesh
2012-04-06 18:13   ` Ulrich Mueller
2012-04-06 18:08 ` Ciaran McCreesh
2012-04-06 18:57 ` David Leverton
2012-04-06 21:25   ` Ulrich Mueller
2012-04-06 21:56     ` David Leverton
2012-04-07  2:44       ` Ulrich Mueller
2012-04-10 10:53         ` Ulrich Mueller
2012-04-10 15:43           ` Zac Medico
2012-04-10 16:30             ` Brian Harring
2012-04-10 16:35               ` Zac Medico
2012-04-10 16:58               ` Ulrich Mueller
2012-04-10 19:23                 ` Zac Medico
2012-04-10 19:25           ` Ciaran McCreesh
2012-04-10 20:13             ` Ulrich Mueller
2012-04-10 20:16               ` Ciaran McCreesh
2012-04-10 21:19                 ` Ulrich Mueller
2012-04-10 21:41                   ` Ciaran McCreesh
2012-04-10 22:11                     ` Ulrich Mueller
2012-04-10 23:20                     ` David Leverton
2012-04-11  8:04                       ` Ulrich Mueller
2012-04-11 16:31                         ` Zac Medico
2012-04-11 18:02                           ` David Leverton
2012-04-11 18:22                             ` Zac Medico
2012-04-12 11:55                           ` Ulrich Mueller
2012-04-15 22:30                             ` Zac Medico
2012-04-15 23:12                               ` Ulrich Mueller
2012-05-13 18:23                             ` David Leverton
2012-05-13 19:00                               ` Ulrich Mueller
2012-05-13 19:11                                 ` [gentoo-pms] [PATCH 1/2] Clarify wording for EAPI parsing David Leverton
2012-05-13 19:35                                   ` Ulrich Mueller
2012-05-13 19:40                                     ` David Leverton
2012-05-13 20:46                                       ` Ulrich Mueller
2012-05-17 10:15                                         ` Ulrich Mueller [this message]
2012-05-13 19:12                                 ` [gentoo-pms] [PATCH 2/2] Require a space before the trailing comment David Leverton

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=20404.53186.682463.406986@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=gentoo-pms@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