Gentoo Logo
Gentoo Spaceship




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
List Archive: gentoo-pms
Navigation:
Lists: gentoo-pms: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-pms@g.o
From: Ulrich Mueller <ulm@g.o>
Subject: Re: [PATCH 1/2] Clarify wording for EAPI parsing
Date: Thu, 17 May 2012 12:15:30 +0200
>>>>> 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


References:
Re: EAPI specification in ebuilds
-- Ulrich Mueller
[PATCH 1/2] Clarify wording for EAPI parsing
-- David Leverton
Re: [PATCH 1/2] Clarify wording for EAPI parsing
-- Ulrich Mueller
Re: [PATCH 1/2] Clarify wording for EAPI parsing
-- David Leverton
Re: [PATCH 1/2] Clarify wording for EAPI parsing
-- Ulrich Mueller
Navigation:
Lists: gentoo-pms: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: [PATCH 1/2] Clarify wording for EAPI parsing
Next by thread:
[PATCH 2/2] Require a space before the trailing comment
Previous by date:
Re: Re: EAPI 5
Next by date:
Including layout.conf in PMS


Updated Jul 18, 2012

Summary: Archive of the gentoo-pms mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.