1 |
Let me first say that I think this revision is much improved, and makes |
2 |
it clearer what we are talking about. |
3 |
|
4 |
As to the stated problem(s): |
5 |
|
6 |
1. "Incompatible change of inherit (e.g. make it look in the package dir |
7 |
too)" |
8 |
A case would need to be made, in my opinion, as to why we would wish to |
9 |
allow this in the first place. The current inherit behavior with |
10 |
eclasses in a central place works well enough. So I think we can |
11 |
disregard this. |
12 |
|
13 |
2. "Add new global scope functions in any sane way" |
14 |
This is a valid use case, as seen by the eapi-2 update. But the way this |
15 |
is currently handled by portage (advising to upgrade the package |
16 |
manager) works. So I don't see a need to change the file extension for |
17 |
this reason. |
18 |
|
19 |
3. "Extend versioning rules in an EAPI - for example, addition of the |
20 |
scm suffix - GLEP54 [1] or allowing more sensible version formats like |
21 |
1-rc1, 1-alpha etc. to match upstream more closely." |
22 |
Apart from GLEP54, I believe our versioning scheme works reasonably |
23 |
well. I don't see any need to match upstream more closely. I'd rather |
24 |
like to keep the more uniform way of handling suffixes like rc and |
25 |
alpha, that we have now. |
26 |
GLEP54 is a valid use case, and I can see the value in that. Even so, |
27 |
using -9999 and variations has worked for us so far, so I'm not |
28 |
convinced GLEP54&55 as a package is a must have. |
29 |
|
30 |
4. "Use newer bash features" |
31 |
This, in my opinion, would potentially be very useful to have. Altho it |
32 |
is certainly possible to continue with bash 3.0 as we have done so far, |
33 |
certain newer features are nice to be able to use. |
34 |
|
35 |
All in all I am still not sold on the perceived problems, and therefor a |
36 |
solution is in my eyes not strictly necessary. Having said that, I do |
37 |
understand people wanting support for newer bash features and GLEP54, so |
38 |
let's look at the possible solutions that have been proposed. |
39 |
|
40 |
|
41 |
Jorge Manuel B. S. Vicetto wrote: |
42 |
> Ulrich Mueller wrote: |
43 |
>>>>>>> On Sun, 17 May 2009, Denis Dupeyron wrote: |
44 |
>>> 2009/5/17 Piotr Jaroszyñski <peper@g.o>: |
45 |
>>>> 1. EAPI-suffixed ebuilds (obviously) |
46 |
>>>> 2. EAPI in the filename with one-time extension change |
47 |
>>>> 3. Easily fetchable EAPI inside the ebuild and one-time extension change |
48 |
>> I'm strongly against 1 and 2 (no need to repeat the old arguments |
49 |
>> here), but I could live with 3. |
50 |
|
51 |
Me too. |
52 |
|
53 |
>>> My preference goes to 3 with a .eb extension and EAPI on the first line. |
54 |
>> Make this "the first non-empty non-comment line". |
55 |
> |
56 |
> As others have commented, we should probably make this the last comment |
57 |
> line in the header. Any suggestions for a specific identification string |
58 |
> or do we simply use '# EAPI="X"' or use a she-bang '#!/<..> EAPI="X"' ? |
59 |
|
60 |
In this case, I'd prefer .eb extension as well. EAPI to be somewhere |
61 |
near the top, I don't care that much about the exact implementation. |
62 |
|
63 |
>> Looks like ".eb" is already taken by some exotic commercial |
64 |
>> application, but I think we can ignore this. |
65 |
> |
66 |
> I like .eb but could also live with .gebuild as was suggested before. |
67 |
|
68 |
I'd rather go for .geb as second choice. I'd rather go shorter than longer. |
69 |
|
70 |
Robert Buchholz wrote: |
71 |
> Judging from this list, fourth option present in the GLEP is |
72 |
> unacceptable for you? |
73 |
> 4. Easily fetchable EAPI inside the ebuild |
74 |
> |
75 |
> From what I understand, the difference between 3 and 4 is that |
76 |
> |
77 |
> (4) would break pre-glep55 Portage versions that see an ebuild with no |
78 |
> metadata cache present if the ebuild uses a future EAPI that |
79 |
> introduces changes as described in the "Current behaviour" section. |
80 |
> (4) would otherwise keep the current workflow the same except |
81 |
> restricting the way the EAPI variable is defined in the ebuild. |
82 |
> |
83 |
> I would argue that most people who are be exposed to repositories that |
84 |
> do not carry a metadata cache (overlays) which use new EAPIs also keep |
85 |
> their portage version current. I'd say go with option (4) now and by |
86 |
> the time EAPI 4 is collected, written up, agreed upon and implemented, |
87 |
> enough time went by so we would not have to introduce an artificial |
88 |
> delay. |
89 |
> And after that, there won't be any delay to avoid breakage anymore. |
90 |
|
91 |
This would still have my preference. |
92 |
|
93 |
Cheers, |
94 |
-- |
95 |
Ben de Groot |
96 |
Gentoo Linux developer (qt, media, lxde, desktop-misc) |
97 |
Gentoo Linux Release Engineering PR liaison |
98 |
______________________________________________________ |