Bug 440158

Summary:	app-admin/eselect - Please keep one (p.masked?) EAPI=0 eselect in tree to support upgrading of old systems via portage-2.1.6.7_p1
Product:	Gentoo Linux	Reporter:	Ian Stakenvicius (RETIRED) <axs>
Component:	New packages	Assignee:	Gentoo eselect Team <eselect>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Ian Stakenvicius (RETIRED) gentoo-dev

2012-10-29 19:33:12 UTC

There may still be occasions where old systems need to be upgraded rather than reinstalled.  Currently portage-2.1.6.7_p1 is being held in the tree, p.masked, for this purpose, however it needs an eselect.

Until recently, eselect-1.2.15 sufficed, but this was removed from the tree.  Would it be possible to keep an EAPI=0 revision of eselect-1.2.18 in the tree (or restore and p.mask 1.2.15) for this purpose, slated for removal when portage-2.1.6.7_p1 is also removed?



Reproducible: Always

Comment 1 Ulrich Müller gentoo-dev

2012-10-29 21:14:13 UTC

EAPI 2 was approved in 2008, therefore I don't see much point in this.

Especially, several of eselect's dependencies have no ebuilds with EAPI 0 left, e.g. sys-apps/coreutils (EAPI 3) or sys-apps/file (EAPI 2).

Comment 2 Ian Stakenvicius (RETIRED) gentoo-dev

2012-10-31 20:00:58 UTC

The EAPI of eselect's direct dependencies (at least for 1.2.15 or 1.2.18) don't matter as long as they exist already on the end-user's system (they did in my case) as eselect can build against the currently-installed version rather than the currently-in-tree one.

That said, I will attempt to solve this via an overlay rather than directly in the portage tree.

Comment 3 Ulrich Müller gentoo-dev

2012-10-31 20:50:40 UTC

I've restored eselect-1.2.15.ebuild from the attic.