Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On 09-11-2007 23:55:51 +0200, Petteri Räty 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-shells/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).
--
Fabian Groffen
Gentoo on a different level
--
gentoo-dev@g.o mailing list
|
|
