1 |
Brian Harring wrote: |
2 |
> |
3 |
> 4) eapi as a function; instead of "EAPI=1", do "eapi 1", required as |
4 |
> the first statement (simplest way). |
5 |
> pros: |
6 |
> - global scope changes can occur (inherit mechanism changes |
7 |
> included). |
8 |
> - expanding on the first, auto inherits (pkg level) are possible- |
9 |
> effectively when eapi gets invoked the manager is in control and |
10 |
> can do whatever is desired setting up the env wise. |
11 |
> - bash version requirements can be leveled (bash parses as it goes, |
12 |
> meaning that essentially it won't parse what follows 'eapi 2' till |
13 |
> that command statement finishes) |
14 |
> - fits w/ the existing semantics nicely enough. |
15 |
> cons: |
16 |
> - mangling the version rules for pkgs still isn't possible; no -scm. |
17 |
> Arguable if -scm is even desired, but being explicit about it not |
18 |
> covering this. |
19 |
> - transition is slightly icky; basically one of the following is |
20 |
> required- |
21 |
> a) for EAPI>=2, do 'eapi 3 || die "upgrade your manager"'. Reason |
22 |
> for this is that current managers obviously lack an eapi function, |
23 |
> to make managers available *now* blow up the || die is required. |
24 |
> This solution can be deployed now, no transition required although |
25 |
> at some point stating "eapi is required retroactively for all |
26 |
> eapis" would be wise to eliminate the need for the || die (cut |
27 |
> support basically for old managers) |
28 |
> b) bashrc trickery, defines an eapi if it's unset. Said eapi |
29 |
> function exports EAPI=$1, optionally triggering a die if the eapi |
30 |
> isn't 0,1,2 (since any later eapi would require a manager upgrade |
31 |
> which would also have the eapi function). |
32 |
> |
33 |
> Personally, if g54 is ixnayed #4 I tend to think is the best option |
34 |
> out there- if g54 is forced in, g55 (or at least something that |
35 |
> adjusts the extension to make it invisible to current managers) is |
36 |
> required. |
37 |
> |
38 |
> Commentary? Tend to think #4 is the most aesthetically pleasing to |
39 |
> folk, but who knows... |
40 |
> ~harring |
41 |
|
42 |
I really like this idea, but nobody else seems to have commented on it. |
43 |
|
44 |
-- |
45 |
Andrew Gaffney http://dev.gentoo.org/~agaffney/ |
46 |
Gentoo Linux Developer Catalyst/Genkernel + Release Engineering Lead |