157370 – emerge --regen should remove stale entries for ebuilds that no longer exist

Bug 157370 - emerge --regen should remove stale entries for ebuilds that no longer exist

Summary: emerge --regen should remove stale entries for ebuilds that no longer exist

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:	InVCS

Depends on:
Blocks:	147007
	Show dependency tree

Reported:	2006-12-06 14:33 UTC by Vlastimil Babka (Caster) (RETIRED)
Modified:	2006-12-08 14:13 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Vlastimil Babka (Caster) (RETIRED) gentoo-dev

2006-12-06 14:33:32 UTC

Right now, stale cache entries stay. While portage itself isn't affected by this, it leaves cruft around. Removing whole /var/cache/edb/dep/ before --regen makes is very very slow.

Comment 1 Zac Medico gentoo-dev

2006-12-07 22:29:40 UTC

This is fixed in svn r5220.

Comment 2 Zac Medico gentoo-dev

2006-12-08 14:13:52 UTC

This has been released in 2.1.2_rc3.