1 |
On Tue, Feb 24, 2009 at 5:21 PM, Petteri Räty <betelgeuse@g.o> wrote: |
2 |
> My notes so far: |
3 |
> |
4 |
> 1) Status quo |
5 |
> - does not allow changing inherit |
6 |
> - bash version in global scope |
7 |
> - global scope in general is quite locked down |
8 |
> |
9 |
> 2) EAPI in file extension |
10 |
> - Allows changing global scope and the internal format of the ebuild |
11 |
> a) .ebuild-<eapi> |
12 |
> - ignored by current Portage |
13 |
> b) .<eapi>.ebuild |
14 |
> - current Portage does not work with this |
15 |
> c) .<eapi>.<new extension> |
16 |
> - ignored by current Portage |
17 |
> |
18 |
> 3) EAPI in locked down place in the ebuild |
19 |
> - Allows changing global scope |
20 |
> - EAPI can't be changed in an existing ebuild so the PM can trust |
21 |
> the value in the cache |
22 |
> - Does not allow changing versioning rules unless version becomes a |
23 |
> normal metadata variable |
24 |
> * Needs more accesses to cache as now you don't have to load older |
25 |
> versions if the latest is not masked |
26 |
> a) <new extension> |
27 |
> b) new subdirectory like ebuilds/ |
28 |
> - we could drop extension all together so don't have to argue about |
29 |
> it any more |
30 |
> - more directory reads to get the list of ebuilds in a repository |
31 |
> c) .ebuild in current directory |
32 |
> - needs one year wait |
33 |
> |
34 |
|
35 |
I don't see the point of some of these... a shorter extension would be |
36 |
nice but not really necessary. |
37 |
|
38 |
.<eapi>.ebuild |
39 |
|
40 |
so like .2.ebuild 'cause that'd work great? |
41 |
smith-1.3.6.2.ebuild better yet vanilla-sources-2.6.28.2.2.ebuild |
42 |
|
43 |
yeah I can see that working out... no it wouldn't |
44 |
|
45 |
or maybe smith-1.3.6.eapi-2.ebuild |
46 |
|
47 |
just too long |
48 |
|
49 |
here's an idea, perhaps not a great one... but perhaps it'll make |
50 |
someone else think... |
51 |
|
52 |
how about this on the first line |
53 |
|
54 |
# eapi-2 |
55 |
|
56 |
and instead of sourcing it, have portage match it with a regex first, |
57 |
figure out the eapi, then source it. |
58 |
|
59 |
I don't know if I really like like what I'm proposing, but I don't see |
60 |
anything else that looks good. |
61 |
-- |
62 |
Caleb Cushing |
63 |
|
64 |
http://xenoterracide.blogspot.com |