-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 10/02/14 08:46 AM, Patrick Lauer wrote: > On 02/10/2014 09:23 PM, Anthony G. Basile wrote: >> 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. > > Right now EAPI 1 and 2 are deprecated, which means repoman prints > some warnings that get ignored and nothing happens.
Back when these were deprecated, the general consensus was that we shouldn't change (especially stable) ebuilds in the tree and just upgrade when we revbump or version bump. Is this still true? If so, I'm wondering how many of those older-EAPI ebuilds are just plain old... -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlL44T8ACgkQ2ugaI38ACPCl1gEAqQYhWVUPjZu05NNAhkhuy36o jlWfu0lJc6irf5Q2vhkA/0NGS29ceLdGjqLbTa8fYPNlQ/4sntpC04tIMuPI4Obm =xnk2 -----END PGP SIGNATURE-----
