On Saturday 21 March 2009 19:37:12 Patrick Lauer wrote:
> Hi all,
>
> with the discussion about EAPI3 we have now 4 (or 7, depending on how you
> count them ;) ) EAPIs available or almost available. This is getting quite
> confusing.
> 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.
> I would set the start of deprecation warnings about 3 months from now and
> the obsoletion quite a time later, maybe 12 months from now, when a
> sufficient amount of ebuilds has been migrated.
>
> Deprecating EAPI1 at the same time would reduce the amount of EAPIs we have
> to think about, but since it has some changes like adding src_prepare
> migration would not be as trivial. So I'd prefer keeping it around a bit
> longer.
>
> Comments?
>
>
> Patrick
The gain obtained by this migration doesnt compensate for the
efford/work one
(we) must put into this. But if we decide to mark EAPI0 as deprecated, first it
would be nice to have a tree cleanup cause it doesn't make much sense to
migrate broken/unmaintained/old/etc ebuilds onto newer EAPIs.-- Markos Chandras (hwoarang) Gentoo Linux Developer KDE/Qt/Sunrise/Sound Web: http://hwoarang.silverarrow.gr
signature.asc
Description: This is a digitally signed message part.
