1 |
On Saturday 21 March 2009 22:26:41 Alec Warner wrote: |
2 |
> >> > > Introducing a policy encouraging moving things that definitely |
3 |
> >> > > aren't in the least bit likely to be a system dep on a bump, sure. |
4 |
> >> > > Making 1 or 2 the default for new packages, sure. But rewriting |
5 |
> >> > > existing things? That's just an accident waiting to happen. |
6 |
> >> > |
7 |
> >> > What kind of accident do you expect to happen? |
8 |
> >> |
9 |
> >> The same kind that always happens when lots of ebuilds get changed. |
10 |
> > |
11 |
> > ... lots of new features and a few bugs that get fixed the next day? Hey, |
12 |
> > that sounds quite bad. And maybe some new herd testers? How rude! |
13 |
> |
14 |
> I don't see the correlation between EAPI bumps and new herd testers. |
15 |
|
16 |
Well, ciaran said that the same thing happens that always happens when lots of |
17 |
ebuilds get changed. Last time I saw that happen (think KDE4) we got some nice |
18 |
herd testers plus a new dev or two, so I am confused too. Maybe ciaran can |
19 |
explain what he meant to say so we don't have to come to unexpected |
20 |
conclusions (that would actually be a quite nice change to the average |
21 |
discussion - saying what you mean instead of hinting at star constellations |
22 |
and the importance of meat loaf) |
23 |
|
24 |
> > So what technical reason(s) do we have to keep archaic EAPIs around |
25 |
> > forever? |
26 |
> None, luckily this is more than a technical project ;) |
27 |
|
28 |
Stop confusing me, antarus, I thought you were against removing eapi0 and now |
29 |
you support the removal? ;) |
30 |
|
31 |
Anyway. Most of the "porting" effort (assuming no other issues sneaking in) |
32 |
would be adding a "EAPI=1" line to ebuilds, which could be done "lazily" on |
33 |
version bumps. There's no rush to get it killed now now now, but in a year we |
34 |
might be at EAPI 5, and then I don't want to be the one writing the docs that |
35 |
split apart what features are where and what syntax is valid and all that. |
36 |
|
37 |
So phasing out eapi0 would be an obvious step towards making things simpler |
38 |
for those of us that don't enjoy studying lists and tables ... |
39 |
|
40 |
|
41 |
Patrick |