On 02/10/2014 07:43 AM, Patrick Lauer wrote:
EAPI 4 becomes deprecated when/if there's a new EAPI allowed in-tree (EAPI 6, most likely)
I am concerned about making this a "rule". While I think its okay for the 4/5/6 move, I'm not sure if it will always be a good idea. 1) "Deprecating" an EAPI can mean breakage --- see my next point. 2) To tie the deprecation of the older EAPI to the introduction of a newer one can delay the introduction of the newer one and possibly needed features. You will connect the question of "are we ready to deprecate X" with the question "we need to introduce Y for needed features a, b and c."
The statement "Deprecating an EAPI can mean breakage" depends on what we mean by "deprecating." I'm assuming here we mean something like repoman won't allow commits at EAPI=1,2,3 but that ebuilds in the tree at those EAPI's will continue working. Eg. dosed which was deprecated in the EAPI 3 to 4 jump.
I think we should look at the question of deprecating EAPI's on and ad hoc basis with discussion on the list and a vote in the council.
--Tony
Please no bikeshedding,
It should be red.
-- Anthony G. Basile, Ph.D. Gentoo Linux Developer [Hardened] E-Mail : bluen...@gentoo.org GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA GnuPG ID : F52D4BBA
