Summary: | add simple "unmerge" functionality to emerge | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Daniel Robbins (RETIRED) <drobbins> |
Component: | Unclassified | Assignee: | Geert Bevin <gbevin> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Daniel Robbins (RETIRED)
2002-01-06 22:34:20 UTC
More complicated version: option to remove packages that depend on the named package. emerge --zap? "depstring" emerge --unmerge? "depstring" Geert -- wanna give this one a shot? If not, I can do it. But I thought I'd offer :) Ok, I'm in for it. :-) Just to not forget : the initial version should either be like this : emerge --unmerge <=cat/pkg-1.0 this uses the dep mechanism to determine which packages should be removed, or similar to the ebuild version : emerge --unmerge /var/db/pkg/cat/pkg-1.1-r2 which does the same as ebuild /var/db/pkg/cat/pkg-1.1-r2pkg-1.1-r2/.ebuild unmerge This has been implemented, would be nice if drobbins could check the changes since I'm still a bit unsure about the whole portage architecture and structure. |