On Tue, 2007-12-25 at 02:43 -0500, Ciaran McCreesh wrote: > 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?
If it's that such a big deal, then simply ensure that 1) no functions are allowed in global scope or 2) eapi is a function and not a variable Thanks Roy PS - Merry Christmas everyone - I'm off to enjoy mine with my family now. I suggest everyone else does the same :) -- [EMAIL PROTECTED] mailing list