From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-dev+bounces-50088-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1S5jBI-0003wo-UY
	for garchives@archives.gentoo.org; Thu, 08 Mar 2012 19:39:21 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 48F8EE08D0;
	Thu,  8 Mar 2012 19:39:12 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	by pigeon.gentoo.org (Postfix) with ESMTP id A1644E03E0
	for <gentoo-dev@lists.gentoo.org>; Thu,  8 Mar 2012 19:38:24 +0000 (UTC)
Received: from localhost (unknown [200.89.69.133])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	(Authenticated sender: aballier)
	by smtp.gentoo.org (Postfix) with ESMTPSA id 41F281B4010
	for <gentoo-dev@lists.gentoo.org>; Thu,  8 Mar 2012 19:38:23 +0000 (UTC)
Date: Thu, 8 Mar 2012 16:38:16 -0300
From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFD: EAPI specification in ebuilds
Message-ID: <20120308163816.4b483aff@gentoo.org>
In-Reply-To: <20313.727.252505.854931@a1i15.kph.uni-mainz.de>
References: <20311.51166.725757.212932@a1i15.kph.uni-mainz.de>
	<20120308185213.6460e780@pomiocik.lan>
	<20313.727.252505.854931@a1i15.kph.uni-mainz.de>
Organization: Gentoo
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Archives-Salt: c5f74fb8-c631-499a-93a0-b29ccf929dea
X-Archives-Hash: 1a160a61a2b542f401fb40e45e7cefd9

On Thu, 8 Mar 2012 20:04:55 +0100
Ulrich Mueller <ulm@gentoo.org> wrote:
> > Err... so what happens if 'new parsing' detects EAPI 4 and 'old
> > parsing' detects EAPI 5?
> 
> This cannot happen for a legal ebuild:
> - If the ebuild is EAPI 4, then sourcing it ("old parsing") must
>   detect EAPI 4.

the problem here may be when "old parsing" will wrongly parse a
malformed EAPI 42 assignment (so that new parsing doesnt detect an
EAPI and assumes its 0) as EAPI 4.
this is a purely hypothetical scenario that will be easily detected if
it ever happens, though :)

anyway, "new parsing" != "old parsing" should trigger a repoman
warning for old EAPIs.

A.