On Dec 25, 2007 2:38 AM, Roy Marples <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-12-25 at 02:26 -0500, Ciaran McCreesh wrote:
> > On Dec 24, 2007 7:53 AM, Roy Marples <[EMAIL PROTECTED]> wrote:
> > > So to obtain EAPI from .ebuild you would always do
> > > EAPI=`. /path/to/ebuild.ebuild; echo "${EAPI}"`
> >
> > Doesn't work with current ebuilds, nor future ebuilds. No points!
>
> Works fine as long as the functions the ebuild has in global scope
> exist. Which would assuming that the ebuild was sourced in a portage
> environment.Ok. So do you use an EAPI 0 environment to do the sourcing, or an EAPI 1 environment, or what? What happens when EAPI 2 changes the behaviour of inherit? What happens when EAPI 2 introduces a new global scope function that sources a new kind of eclass that current package managers don't support? -- Ciaran McCreesh -- [EMAIL PROTECTED] mailing list
