Ciaran McCreesh schrieb: > On Sun, 11 Mar 2012 17:18:45 +0100 > Chí-Thanh Christopher Nguyễn <chith...@gentoo.org> wrote: >> Assume a new version 13.37 of your package manager drops EAPI=1 >> support. So package-manager-13.37.ebuild checks in pkg_pretend() if >> any EAPI=1 package is installed on the system. If yes, then it >> aborts, telling the user to get rid of the package first. > Oh, now I get it. There are two issues there... > > First, doing that is going to screw things up for users who have two > package managers installed, unless you make every package mangler's > package aware of every package mangler.
As long as the package managers are installed through ebuilds, they should observe each other's pkg_pretend() > Second, there's not a way of getting the information you need to figure > that out using current EAPIs. That I suspected, that's why I asked about feasibility. "grep 1 $(portageq vdb_path)/*/*/EAPI && die" might work for portage and its current VDB layout. One problem that remains with this approach is what happens if an EAPI=1 package is in the list of packages to be merged along with the new package manager. > It's also not really worth it at the moment. There aren't any major > architectural changes between EAPIs just now, so removing support for > an EAPI won't allow any majorly nasty code to be removed from a package > manager. It might be worth revisiting this if we ever switch to EAPIs > that allow us to kill off VDB, for example. Yes, tommy already told me on IRC that there is no incentive for package managers to drop EAPI support at this time. Best regards, Chí-Thanh Christopher Nguyễn
