| 1 |
On Sat, 21 Mar 2009 21:53:16 +0100 |
| 2 |
Patrick Lauer <patrick@g.o> wrote: |
| 3 |
> Because, as you have noticed before, developers get confused which |
| 4 |
> eapi has which features available. And eapi1 is a superset of eapi0, |
| 5 |
> so we don't have to rewrite tons of things. |
| 6 |
|
| 7 |
So? When people do new things, they can move the EAPI forward. That's |
| 8 |
not a reason to modify existing things. |
| 9 |
|
| 10 |
> > Introducing a policy encouraging moving things that definitely |
| 11 |
> > aren't in the least bit likely to be a system dep on a bump, sure. |
| 12 |
> > Making 1 or 2 the default for new packages, sure. But rewriting |
| 13 |
> > existing things? That's just an accident waiting to happen. |
| 14 |
> |
| 15 |
> What kind of accident do you expect to happen? |
| 16 |
|
| 17 |
The same kind that always happens when lots of ebuilds get changed. |
| 18 |
|
| 19 |
-- |
| 20 |
Ciaran McCreesh |
Archives