Summary: | Add more --reinstall options | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Chris Gianelloni <wolf31o2> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 144480 |
Description
Chris Gianelloni
2009-07-01 00:43:08 UTC
What about --emptytree? Is there a case where you'd only want to do the packages directly in the set and not their dependencies? Since portage-2.1.9 we support separate @world, @system, and @selected sets, where @selected is just the packages from /var/lib/portage/world, and @world is the sum of @selected and @system. I don't think we should provide several ways to do the same thing without a very good reason. Use package sets for package sets and the various options like --newuse, --update, etc to apply configuration changes to the system. There is no need for consistency between the two kinds of things, since they deal with two different concepts (a set a of packages vs packages for which the configuration has changed). |