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 1Iqc6O-0005KX-8V for garchives@archives.gentoo.org; Fri, 09 Nov 2007 22:13:24 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lA9MBp5F025393; Fri, 9 Nov 2007 22:11:51 GMT Received: from osiris.cheops.ods.org (osiris.cheops.ods.org [80.127.25.226]) by robin.gentoo.org (8.14.2/8.14.0) with ESMTP id lA9M7O4D017092 for ; Fri, 9 Nov 2007 22:07:24 GMT Received: from tefnut.cheops.ods.org ([2001:888:1022:0:211:24ff:fe37:e46e] helo=gentoo.org) by osiris.cheops.ods.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1Iqc0Z-0003BU-Oa for gentoo-dev@lists.gentoo.org; Fri, 09 Nov 2007 23:07:23 +0100 Date: Fri, 9 Nov 2007 23:07:24 +0100 From: Fabian Groffen To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] RFC: Place of EAPI variable in ebuild Message-ID: <20071109220724.GK19739@gentoo.org> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <4734D767.1080900@gentoo.org> 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=utf-8 Content-Disposition: inline In-Reply-To: <4734D767.1080900@gentoo.org> User-Agent: Mutt/1.5.17 (Darwin 8.10.0, VIM - Vi IMproved 7.1) Organization: Gentoo Foundation, Inc. Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id lA9MBp6x025393 X-Archives-Salt: 16f06b01-dc22-4153-ad13-a0d850040be1 X-Archives-Hash: a003ed756d2c1709ac05be1da95bc70e On 09-11-2007 23:55:51 +0200, Petteri R=C3=A4ty wrote: > Usually it's best that ebuild variables follow the order that is in > skel.ebuild. So know we should decide where to place EAPI. I suggest we > put it it after LICENSE as that's where the more technical stuff like > SLOT starts. Attached a patch for skel.ebuild. Just my 2 cents, I have placed EAPI right after the # $Header: line of each ebuild, as I felt that it was the first thing to know of the ebuild, as it describes how you possibly have to process the rest of the ebuild. Examples can be found in the prefix overlay, e.g. http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay/app-shel= ls/bash/bash-3.2_p17-r00.1.ebuild It has the advantage for me that EAPI is never hidden away somewhere down the ebuild, and it is just inserted by a simple bash script automagically (eapify in this case). --=20 Fabian Groffen Gentoo on a different level --=20 gentoo-dev@gentoo.org mailing list