| 1 |
On Saturday 21 March 2009 21:21:47 Ciaran McCreesh wrote: |
| 2 |
> On Sat, 21 Mar 2009 18:37:12 +0100 |
| 3 |
> |
| 4 |
> Patrick Lauer <patrick@g.o> wrote: |
| 5 |
> > To make our lives easier I would suggest deprecating EAPI0 and |
| 6 |
> > migrating existing ebuilds over some time to EAPI1 or higher until |
| 7 |
> > EAPI0 can be obsoleted at some point in the future. |
| 8 |
> |
| 9 |
> Uh. Why? |
| 10 |
Because, as you have noticed before, developers get confused which eapi has |
| 11 |
which features available. And eapi1 is a superset of eapi0, so we don't have |
| 12 |
to rewrite tons of things. |
| 13 |
|
| 14 |
> Introducing a policy encouraging moving things that definitely aren't |
| 15 |
> in the least bit likely to be a system dep on a bump, sure. Making 1 or |
| 16 |
> 2 the default for new packages, sure. But rewriting existing things? |
| 17 |
> That's just an accident waiting to happen. |
| 18 |
What kind of accident do you expect to happen? |
| 19 |
|
| 20 |
Patrick |
Archives