[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] Deprecate EAPIs 0 and 1?
From:       Rich Freeman <rich0 () gentoo ! org>
Date:       2010-12-31 21:38:58
Message-ID: AANLkTik=VjGaMf0cTXFgOSuSRDeRaUJxf2Btqe+g1OHN () mail ! gmail ! com
[Download RAW message or body]

On Fri, Dec 31, 2010 at 12:53 PM, Mike Frysinger <vapier@gentoo.org> wrote:
>
> personally, i dont see a problem here.  what actual burden is there for
> continuing supporting EAPI 0/1 ?  i dont think we should go around deprecating
> things for the pure fun of it.
> -mike
>

I tend to agree, unless of course the maintainers of the various
package managers chime in and say that some aspect of some particular
EAPI requires them to maintain a lot of legacy code.  Then I'd be all
for dropping some.

However, with upwards of 70%+ of the tree being pre-EAPI-3, do we
really want to go around tweaking all those ebuilds just so that they
work exactly like they already work (if we don't mess anything up)?
I'm sure lots of packages are maintainer-needed, so are we going to do
a massive removal of otherwise-working packages just because of their
EAPI (I"m fine with cleaning broken packages, but why touch working
ones)?

Sure, the new EAPIs are nice, and I'm sure that devs creating new
ebuilds will follow whatever is in the devmanual (which obviously
would only reference the new way of doing things) so over time things
will take care of themselves.  Why force a change?

Again, if this is causing the package manager / repoman / etc
maintainers problems, then I'm fine with simplifying the landscape...

Rich


[prev in list] [next in list] [prev in thread] [next in thread]