On Fri, 31 Dec 2010 12:02:32 +0100
Ulrich Mueller <[email protected]> wrote:
> So maybe it's about time that we deprecate EAPIs 0 and 1 for new
> ebuilds. As a first step, a warning could be added to repoman that
> would be triggered whenever a new ebuild with an EAPI less than 2 is
> committed.
I don't see a reason to deprecate an EAPI, unless you are out to stop a
specific feature from being used that was introduced in a later EAPI
and breaks the earlier EAPI. Those ebuilds should be converted or
otherwise taken care of, but it still wouldn't deprecate the older
EAPI as a whole.
jer
