On Sun, Mar 11, 2012 at 04:14:33PM +0100, Ch??-Thanh Christopher Nguy???n wrote: > Ciaran McCreesh schrieb: > >> Is there really much of a benefit to this? I guess for anybody who > >> runs scripts to mass-manipulate ebuilds it might be helpful, but I > >> think all the package managers planned on supporting all the EAPIs for > >> quite a while longer. > > We have to support them indefinitely. It's not possible to uninstall a > > package whose EAPI is unknown. > > > > Would it be feasible to do a pkg_pretend() check and refuse > install/upgrade if packages with unsupported EAPI are detected?
The question should be "is it worth doing it", rather than "can we hack out something". As Ciaran said, PM's are going to be supporting EAPI1 indefinitely- it's zero cost to do so at this point. Thus doing what you're proposing doesn't gain us anything but complexity. If people want to enforce the eapi1 is no longer used in the gentoo repo, that's fine- we stick a list of acceptable EAPI's into its layout.conf. If you want to block EAPI1 from being further used, go that route; at least for pkgcore (and presumably paludis, likely portage), ripping out EAPI1 is unlikely to occur anything this side of 2015. ~brian
