1 |
Let's try something new. I would like to get opinions from as many |
2 |
people as possible about GLEP 55 and alternatives listed here in order |
3 |
to get some idea what the general developer pool thinks. Everyone is |
4 |
only allowed to post a single reply to this thread in order to make it |
5 |
easy to read through. The existing thread should be used for actual |
6 |
discussion about the GLEP and the alternatives. This should be a useful |
7 |
experiment to see if we can control ourselves :) |
8 |
|
9 |
My notes so far: |
10 |
|
11 |
1) Status quo |
12 |
- does not allow changing inherit |
13 |
- bash version in global scope |
14 |
- global scope in general is quite locked down |
15 |
|
16 |
2) EAPI in file extension |
17 |
- Allows changing global scope and the internal format of the ebuild |
18 |
a) .ebuild-<eapi> |
19 |
- ignored by current Portage |
20 |
b) .<eapi>.ebuild |
21 |
- current Portage does not work with this |
22 |
c) .<eapi>.<new extension> |
23 |
- ignored by current Portage |
24 |
|
25 |
3) EAPI in locked down place in the ebuild |
26 |
- Allows changing global scope |
27 |
- EAPI can't be changed in an existing ebuild so the PM can trust |
28 |
the value in the cache |
29 |
- Does not allow changing versioning rules unless version becomes a |
30 |
normal metadata variable |
31 |
* Needs more accesses to cache as now you don't have to load older |
32 |
versions if the latest is not masked |
33 |
a) <new extension> |
34 |
b) new subdirectory like ebuilds/ |
35 |
- we could drop extension all together so don't have to argue about |
36 |
it any more |
37 |
- more directory reads to get the list of ebuilds in a repository |
38 |
c) .ebuild in current directory |
39 |
- needs one year wait |
40 |
|
41 |
Regards, |
42 |
Petteri |