1 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
2 |
> People are struggling with the one level scheme we have now. We're |
3 |
> already having to produce fancy tables and summaries for new EAPIs |
4 |
> because people can't keep track of when features came along. Two |
5 |
> levels just means no-one will remember any of it. |
6 |
|
7 |
I disagree with your assertion that people are struggling - I think |
8 |
things are very nicely documented in PMS and the devmanual, which are |
9 |
where all EAPI changes should be documented in the future, regardless |
10 |
if you specify the EAPI in the file, the extension, or both. |
11 |
|
12 |
Two levels really just means that any fancy tables will have to have |
13 |
one extra row (or perhaps a series of fancy tables) and any summaries |
14 |
will have to have an extra section added whenever a new filename |
15 |
extension becomes necessary. |
16 |
|
17 |
> For the package manager, it's just a bit of added mess, not any major |
18 |
> difficulty. |
19 |
|
20 |
This is good to know, thank you for the clarification. |
21 |
|
22 |
> People are opposed to 55 because of a knee-jerk reaction against |
23 |
> changing file extensions and against doing anything that comes from |
24 |
> the great Satan and all his little minions... If you're going to throw |
25 |
> an equivalent but supposedly compromising solution at people, go for |
26 |
> '.eapi3.eb' instead. |
27 |
|
28 |
I can't speak to anyone's motivations or religious beliefs other than my |
29 |
own here, but the opposition I have heard most often in this thread |
30 |
is something like: "I don't like it when the file extension changes so |
31 |
often". Some people site historical president or the way other software |
32 |
does things, or whatever -> doesn't really matter. |
33 |
|
34 |
What does matter is that some people don't like it when the file |
35 |
extension changes very often. I think my solution is a valid compromise |
36 |
because it balances, in my opinion, the two camps, whose arguments I |
37 |
summarize as: |
38 |
|
39 |
glep-55'ers: "I don't care if the file extension changes all the time, I |
40 |
just want a solution that works and is reasonably future-proof" |
41 |
|
42 |
Anti-55'ers: "I don't want the file extension to change ever, but I |
43 |
would agree that for major-enough changes it may be required |
44 |
sometimes" |
45 |
|
46 |
If I understand the '.eapi3.eb' to which you make passing reference, |
47 |
this is just a fancy hand-wavy way to say "Look, the true .eb |
48 |
extension won't ever change, just the .eapi3 part which isn't |
49 |
technically the extension..." which isn't a compromise at all - It's an |
50 |
attempt to (cleverly?) obfuscate where in the filename the EAPI is |
51 |
stored. |
52 |
|
53 |
-- |
54 |
Jim Ramsay |
55 |
Gentoo Developer (rox/fluxbox/gkrellm) |