| 1 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 2 |
> On Tue, 24 Feb 2009 15:07:29 -0500 |
| 3 |
> Jim Ramsay <lack@g.o> wrote: |
| 4 |
> > I think |
| 5 |
> > things are very nicely documented in PMS and the devmanual, which |
| 6 |
> > are where all EAPI changes should be documented in the future, |
| 7 |
> > regardless if you specify the EAPI in the file, the extension, or |
| 8 |
> > both. |
| 9 |
> |
| 10 |
> They only ended up nicely documented after people moaned a lot that |
| 11 |
> they were having a hard time keeping track of EAPIs... |
| 12 |
|
| 13 |
You can't possibly be suggesting that everyone will be able to keep an |
| 14 |
ever-increasing number of feature sets in his or her mind, or that |
| 15 |
changing from a two-level to a one-level EAPI definition will remove |
| 16 |
the need for documentation going forward, so I'm not sure what you mean |
| 17 |
by this. |
| 18 |
|
| 19 |
> > Two levels really just means that any fancy tables will have to have |
| 20 |
> > one extra row (or perhaps a series of fancy tables) and any |
| 21 |
> > summaries will have to have an extra section added whenever a new |
| 22 |
> > filename extension becomes necessary. |
| 23 |
> |
| 24 |
> It'll mean people will carry on having to use the tables, and won't |
| 25 |
> start remembering things as time goes on. |
| 26 |
|
| 27 |
See comment above. The need for documentation will only increase going |
| 28 |
forward as new and varied EAPI definitions are created. |
| 29 |
|
| 30 |
> > If I understand the '.eapi3.eb' to which you make passing reference, |
| 31 |
> > this is just a fancy hand-wavy way to say "Look, the true .eb |
| 32 |
> > extension won't ever change, just the .eapi3 part which isn't |
| 33 |
> > technically the extension..." which isn't a compromise at all - It's |
| 34 |
> > an attempt to (cleverly?) obfuscate where in the filename the EAPI |
| 35 |
> > is stored. |
| 36 |
> |
| 37 |
> Yup. And yet there're people who are perfectly happy with .eapi3.eb |
| 38 |
> who hate GLEP 55. That should tell you all you need to know about |
| 39 |
> what's going on here... |
| 40 |
|
| 41 |
Seriously? That's scary. But hey, if that's actually going to get |
| 42 |
more people behind this, let's do it instead. |
| 43 |
|
| 44 |
-- |
| 45 |
Jim Ramsay |
| 46 |
Gentoo Developer (rox/fluxbox/gkrellm/vim) |
Archives