Summary: | When unmerging, Portage should record files it didn't delete | ||
---|---|---|---|
Product: | Portage Development | Reporter: | DC <gtbgs> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
DC
2006-01-20 02:19:09 UTC
No central file db- this is why portage relies on mdm5's and mtime to determine if the file needs be removed. That is the underlying cause of orphaning files on unmerge. That's also why this request is questionable ;) . To do what you're asking, we need a central file db to determiine if the file actually _was_ orphaned- collision-protect does makes this easier, but it's not a required feature, thus an actual centrak db is required. Mind you I'm not excusing orphaning files- that bugs the hell out of me personally. Just explaining the reasons, and why their is no orphan list- if we implemented that list, we would already solve the orphaning problem. Reopening for duping *** This bug has been marked as a duplicate of bug 159165 *** |