Hi,

Duncan <1i5t5.duncan@cox.net>:
> > Potentially the developer could just manually put the EAPI in the
> > manifest (or use a tool to do this).  Obviously this is an extra
> > step when adding ebuilds to the tree, but that would completely
> > address the issues with sourcing builds.
> 
> That's an interesting idea.  A "manual" method for putting the EAPI
> in the manifest, thus bypassing the chicken/egg issue of needing to
> need the EAPI to source the ebuild... to get the EAPI.

 Having the EAPI stored outside the ebuild's scope is generally a bad
idea, because someone has to tell you that the ebuild you just
downloaded from Bugzilla is EAPI x.  And the package manager will be
totally confused when assuming an EAPI that is wrong.  So the EAPI
should be stored inside (best solution regarding giving ebuilds away)
or in the file name (best compromise regarding the whole situation.

V-Li

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://www.faulhammer.org/>