On Saturday 21 of March 2009 21:53:16 Patrick Lauer wrote: > On Saturday 21 March 2009 21:21:47 Ciaran McCreesh wrote: > > On Sat, 21 Mar 2009 18:37:12 +0100 > > > > Patrick Lauer <patr...@gentoo.org> wrote: > > > To make our lives easier I would suggest deprecating EAPI0 and > > > migrating existing ebuilds over some time to EAPI1 or higher until > > > EAPI0 can be obsoleted at some point in the future. > > > > Uh. Why? > > Because, as you have noticed before, developers get confused which eapi has > which features available. And eapi1 is a superset of eapi0, so we don't > have to rewrite tons of things. >
Spend more time to teach them. It's easier to developers make sure they do things ok than users spending their time to figure out what's wrong. Personally i don't like the idea of deprecating EAPI0 since it may break many servers. Eg. our border router at work isn't upgraded regulary. I spent much time lately to upgrade it with problems like portage vs. bash and so. So the last thing i'd like to see now in portage is implementing your proposal. > > Introducing a policy encouraging moving things that definitely aren't > > in the least bit likely to be a system dep on a bump, sure. Making 1 or > > 2 the default for new packages, sure. But rewriting existing things? > > That's just an accident waiting to happen. > > What kind of accident do you expect to happen? > > Patrick
