1 |
On Tue, 2007-12-25 at 02:43 -0500, Ciaran McCreesh wrote: |
2 |
> On Dec 25, 2007 2:38 AM, Roy Marples <roy@×××××××.name> wrote: |
3 |
> > On Tue, 2007-12-25 at 02:26 -0500, Ciaran McCreesh wrote: |
4 |
> > > On Dec 24, 2007 7:53 AM, Roy Marples <roy@×××××××.name> wrote: |
5 |
> > > > So to obtain EAPI from .ebuild you would always do |
6 |
> > > > EAPI=`. /path/to/ebuild.ebuild; echo "${EAPI}"` |
7 |
> > > |
8 |
> > > Doesn't work with current ebuilds, nor future ebuilds. No points! |
9 |
> > |
10 |
> > Works fine as long as the functions the ebuild has in global scope |
11 |
> > exist. Which would assuming that the ebuild was sourced in a portage |
12 |
> > environment. |
13 |
> |
14 |
> Ok. So do you use an EAPI 0 environment to do the sourcing, or an EAPI |
15 |
> 1 environment, or what? |
16 |
|
17 |
If it's that such a big deal, then simply ensure that |
18 |
|
19 |
1) no functions are allowed in global scope |
20 |
or |
21 |
2) eapi is a function and not a variable |
22 |
|
23 |
Thanks |
24 |
|
25 |
Roy |
26 |
|
27 |
PS - Merry Christmas everyone - I'm off to enjoy mine with my family |
28 |
now. I suggest everyone else does the same :) |
29 |
|
30 |
-- |
31 |
gentoo-dev@g.o mailing list |