1 |
Ciaran McCreesh wrote: |
2 |
> |
3 |
> Ok. What's the EAPI for the following ebuild that's written in an EAPI |
4 |
> that hasn't been published yet? And how would I extract it? |
5 |
> |
6 |
> # Copyright blah blah |
7 |
> |
8 |
> import vim-spell using language="en" |
9 |
> |
10 |
|
11 |
Counterexample. How do you determine the eapi for the following file, |
12 |
which uses an EAPI that is yet unpublished - but which specifies that |
13 |
the EAPI NOT go in the filename: foo-1.2.ebuild |
14 |
|
15 |
Obviously if you go down one road, and then intentionally change things |
16 |
to go down another then old stuff won't work. Any package manager that |
17 |
depends on having the EAPI in the filename won't work if a decision is |
18 |
later made to remove the EAPI from the filename. |
19 |
|
20 |
Making a decision to put the EAPI in the filename for all time doesn't |
21 |
seem any less restricting than making a decision to put EAPI=1 or |
22 |
EAPI="1" in the ebuild for all time. And the latter is a whole lot less |
23 |
messy as far as I can see. |
24 |
|
25 |
So far the only objection I've seen to putting EAPI in the ebuild is |
26 |
that at some point in the future we might want to do it differently. |
27 |
Well, that is nice, but the same issue would apply to putting it in the |
28 |
filename - we could want to change that someday too. And if we put it |
29 |
in the filename why would we want to put it in a function or whatever |
30 |
inside the ebuild as well? Wouldn't that just be redundant. |
31 |
|
32 |
Sure, by not putting it in the filename we restrict ourselves a little |
33 |
from changing things later. However, if we do put in the filename we |
34 |
seem to already have a mass of folks who would want to change it RIGHT |
35 |
NOW. |
36 |
|
37 |
And if the whole point of this is to allow massive changes to ebuild |
38 |
format - why not wait until a need for such a change exists before |
39 |
instituting it. Why not defer this GLEP until it has some benefit and |
40 |
not just pain associated with it? |