Bug 66292

Summary:	Portage should respect versions of packages without an ebuild in portage
Product:	Portage Development	Reporter:	Henrik Sankala <hensan>
Component:	Enhancement/Feature Requests	Assignee:	Portage team <dev-portage>
Status:	RESOLVED INVALID
Severity:	enhancement
Priority:	High
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description Henrik Sankala 2004-10-04 02:27:50 UTC

Problem:

Sometimes I don't feel that upgrading a package to a new revision is motivated, so I mask the revision. All is well until the devs remove the ebuild for the version I have installed. Now all of the sudden, my version is no longer good enough to satisfy dependencies, and when you do a emerge -uD world, you either get a depgraph creation failure or portage wants to install a old version of my package.


Requested solution:

Let an installed version of a package continue to satisfy a dependency even if the ebuild for it no longer exists in portage (as long as the version number of the installed package satisfies the dependency of course).

Comment 1 Nicholas Jones (RETIRED) gentoo-dev

2004-10-09 13:45:48 UTC

No.

The lack of an ebuild indicates it is deprecated or outdated. If you wish
to maintain such a verysion, use an overlay.