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 ) id 1S5i08-00026O-K3 for garchives@archives.gentoo.org; Thu, 08 Mar 2012 18:23:44 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DF4B8E09C7; Thu, 8 Mar 2012 18:23:34 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 8672BE0984 for ; Thu, 8 Mar 2012 18:22:49 +0000 (UTC) Received: from [192.168.42.250] (staff-wireless.saddleback.edu [209.129.85.50]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 7DBBF1B4037 for ; Thu, 8 Mar 2012 18:22:48 +0000 (UTC) Message-ID: <4F58F8F4.8020002@gentoo.org> Date: Thu, 08 Mar 2012 10:22:44 -0800 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.1) Gecko/20120304 Thunderbird/10.0.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] RFD: EAPI specification in ebuilds References: <20311.51166.725757.212932@a1i15.kph.uni-mainz.de> <20120308185213.6460e780@pomiocik.lan> In-Reply-To: <20120308185213.6460e780@pomiocik.lan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 79660201-c94f-4a00-b6e5-15232ed50c8e X-Archives-Hash: 6b930139ef2fef651adfcaf3e293859a On 03/08/2012 09:52 AM, Micha=C5=82 G=C3=B3rny wrote: > On Wed, 7 Mar 2012 21:41:02 +0100 > Ulrich Mueller wrote: >> 1b) It is only applied for EAPI 5 and later (which means that the >> result of the EAPI parsing would be discarded for earlier EAPIs). > > Err... so what happens if 'new parsing' detects EAPI 4 and 'old > parsing' detects EAPI 5? Or more exactly, how does it know when > an older EAPI is used if it is supposed to not use the value it uses to > detect EAPI? We can simply detect this case and treat it as an error. The purpose of=20 the "discarded for earlier EAPIs" part is to allow more variance for=20 older EAPIs, and treating this case as an error will probably affect=20 zero or a negligible number of older ebuilds in practice. --=20 Thanks, Zac