1 |
On 23:20 Mon 17 Dec , Piotr Jaroszyński wrote: |
2 |
> Abstract |
3 |
> ======== |
4 |
> |
5 |
> This GLEP proposes usage of EAPI-suffixed file extensions for ebuilds (for |
6 |
> example, foo-1.2.3.ebuild-1). |
7 |
> |
8 |
> Motivation |
9 |
> ========== |
10 |
> |
11 |
> Including EAPI in the ebuild file extension has the following advantages: |
12 |
> |
13 |
> * Possibility to extend the versioning rules in an EAPI, and to use them |
14 |
> immediately in the Gentoo tree. For example, addition of the scm suffix - |
15 |
> GLEP54 [#GLEP54]_. |
16 |
> |
17 |
> * Possibility to extend the behaviour of inherit and add new global scope |
18 |
> functions (as a result of not sourcing ebuilds with unsupported EAPI). |
19 |
|
20 |
Here's some other ideas for how to express EAPI. What if we: |
21 |
|
22 |
Used EAPI-named subdirectories instead of tagging it into the filename? |
23 |
|
24 |
Used (and required) filesystem extended attributes? |
25 |
|
26 |
Stuck ranges into metadata.xml for which EAPIs applied? |
27 |
|
28 |
Thanks, |
29 |
Donnie |
30 |
-- |
31 |
gentoo-dev@g.o mailing list |