On Thu, 30 Aug 2012 16:05:52 -0400 Michael Mol <[email protected]> wrote: > Compile a list of existing ebuilds which depend on old EAPIs, and > you've got a TODO list. (eclasses, I don't know; I don't know if > eclasses explicitly express EAPI compatibility in metadata) Once that > list is cleared, yes, you can assume there are no ebuilds with a > specified EAPI of 0. I'd presume it would have been made widely known > that new ebuilds shouldn't use the old EAPI by that point, and so > support for the deprecated EAPI level can be abandoned.
You can't uninstall a package if you don't support its EAPI. The "remove code" benefit applies to eclasses, not package manglers. -- Ciaran McCreesh
signature.asc
Description: PGP signature
