From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1J4QVP-0000zd-Tj for garchives@archives.gentoo.org; Tue, 18 Dec 2007 00:40:20 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lBI0dHQG017604; Tue, 18 Dec 2007 00:39:17 GMT Received: from caine.easynet.fr (smarthost151.mail.easynet.fr [212.180.1.151]) by robin.gentoo.org (8.14.2/8.14.0) with ESMTP id lBI0bMVl015204 for ; Tue, 18 Dec 2007 00:37:22 GMT Received: from easyconnect2121138-64.clients.easynet.fr ([212.11.38.64] helo=eusebe) by caine.easynet.fr with esmtp (Exim 4.63) (envelope-from ) id 1J4QSX-00018a-L4 for gentoo-dev@lists.gentoo.org; Tue, 18 Dec 2007 01:37:22 +0100 Date: Tue, 18 Dec 2007 01:36:51 +0100 From: Thomas de Grenier de Latour To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [GLEP] Use EAPI-suffixed ebuilds (.ebuild-EAPI) Message-ID: <20071218013651.58f4f565@eusebe> In-Reply-To: <20071218001855.78c1864c@blueyonder.co.uk> References: <200712172320.01988.peper@gentoo.org> <47671006.2020808@gentoo.org> <20071218001855.78c1864c@blueyonder.co.uk> X-Mailer: Claws Mail 3.1.0 (GTK+ 2.12.1; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@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: 0e086b20-04e5-4d97-821a-58dab3c7a155 X-Archives-Hash: a06ce5bbae303e3f7cf7093088d34883 On 2007/12/18, Ciaran McCreesh wrote: > On Mon, 17 Dec 2007 17:10:46 -0700 > Joe Peterson wrote: > > I probably missed some of the stuff leading up to this GLEP, but > > what is the problem with having the EAPI in the file and > > determining it by looking at the file contents? > > Motivation, second bullet point: > > | Possibility to extend the behaviour of inherit and add new global > | scope functions (as a result of not sourcing ebuilds with > | unsupported EAPI). Why can't it be in the file but readable without sourcing? For instance, it could be mandatory that EAPI=X, if present, must be the first non-blank and non-comment line of the ebuild (and it would then be checked after sourcing, if the ebuild is sourced, to bug on cases where it's redefined or unset afterwards). -- TGL. -- gentoo-dev@gentoo.org mailing list