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-50119-garchives=archives.gentoo.org@lists.gentoo.org>) id 1S639W-0004uk-Fa for garchives@archives.gentoo.org; Fri, 09 Mar 2012 16:58:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 14DB3E091E; Fri, 9 Mar 2012 16:58:35 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 69E35E07EA for <gentoo-dev@lists.gentoo.org>; Fri, 9 Mar 2012 16:57:54 +0000 (UTC) Received: from [192.168.26.5] (ip98-164-193-252.oc.oc.cox.net [98.164.193.252]) (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 B617A644A6 for <gentoo-dev@lists.gentoo.org>; Fri, 9 Mar 2012 16:57:53 +0000 (UTC) Message-ID: <4F5A3690.30804@gentoo.org> Date: Fri, 09 Mar 2012 08:57:52 -0800 From: Zac Medico <zmedico@gentoo.org> 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: <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 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> <4F57DDB5.3090503@orlitzky.com> <20120308130310.69c3c714@pomiocik.lan> <4F58D6A5.7070804@orlitzky.com> <20120308182844.11201771@pomiocik.lan> <4F58F103.5010503@orlitzky.com> <20120308175345.2c4b72ff@googlemail.com> <4F58FC55.7070005@orlitzky.com> <20120308184820.108fc30c@googlemail.com> <4F592612.6050203@orlitzky.com> <20120309060424.09cdce1e@pomiocik.lan> <4F599692.9050503@orlitzky.com> <4F599A61.8010600@gentoo.org> <4F5A16C5.7050303@orlitzky.com> <4F5A1C46.7080005@gentoo.org> <4F5A2001.30309@orlitzky.com> <4F5A2495.4060305@gentoo.org> <20120309125126.186969f9@gentoo.org> <4F5A28B6.2010404@gentoo.org> <4F5A34A8.4080200@orlitzky.com> In-Reply-To: <4F5A34A8.4080200@orlitzky.com> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 61e468d2-cf52-4f65-b9f9-cb50feda1010 X-Archives-Hash: 044282b22b7e3171970a35f52e41c894 On 03/09/2012 08:49 AM, Michael Orlitzky wrote: > The point was to be able to get the EAPI without crashing if the ebuild > uses newer features. If you can get the EAPI without sourcing, that > obviously accomplishes the goal. But there are other goals, too, like > not limiting the syntax of the EAPI assignment. I was just trying to > think up something that addresses them all. Yeah, but you compromised on what can be considered our primary goal, which is to obtain the EAPI without sourcing the ebuild. > In any case, yeah, it would crash and burn if someone synced his tree > with an ancient version of portage. But so would the comment solution. Don't forget the possibility of bash syntax extensions triggering a syntax error [1]. The comment and bash assignment solutions are immune to that because bash is exceedingly unlikely to break backward compatibility in the comment and bash assignment syntax. [1] http://archives.gentoo.org/gentoo-dev/msg_2c1fbbb32f5bc47756303ca18055bee4.xml -- Thanks, Zac