| 1 |
Thanks Petteri, |
| 2 |
|
| 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 |
lets move on! |
| 10 |
|
| 11 |
> |
| 12 |
> 2) EAPI in file extension |
| 13 |
> - Allows changing global scope and the internal format of the ebuild |
| 14 |
> a) .ebuild-<eapi> |
| 15 |
> - ignored by current Portage |
| 16 |
> b) .<eapi>.ebuild |
| 17 |
> - current Portage does not work with this |
| 18 |
> c) .<eapi>.<new extension> |
| 19 |
> - ignored by current Portage |
| 20 |
|
| 21 |
2 a) and 2 c) are fine by me. |
| 22 |
|
| 23 |
> |
| 24 |
> 3) EAPI in locked down place in the ebuild |
| 25 |
> - Allows changing global scope |
| 26 |
> - EAPI can't be changed in an existing ebuild so the PM can trust |
| 27 |
> the value in the cache |
| 28 |
> - Does not allow changing versioning rules unless version becomes a |
| 29 |
> normal metadata variable |
| 30 |
> * Needs more accesses to cache as now you don't have to load older |
| 31 |
> versions if the latest is not masked |
| 32 |
> a) <new extension> |
| 33 |
> b) new subdirectory like ebuilds/ |
| 34 |
> - we could drop extension all together so don't have to argue about |
| 35 |
> it any more |
| 36 |
> - more directory reads to get the list of ebuilds in a repository |
| 37 |
> c) .ebuild in current directory |
| 38 |
> - needs one year wait |
| 39 |
|
| 40 |
no thanks. |
| 41 |
|
| 42 |
> |
| 43 |
> Regards, |
| 44 |
> Petteri |
| 45 |
|
| 46 |
regards |
| 47 |
Thilo |
Archives