Summary: | force emerge @preserved-rebuild even if some packages are lacking | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Helmut Jarausch <jarausch> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra, kingjon3377, zeekec |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=287900 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 328343 | ||
Bug Blocks: | 144480, 240323 |
Description
Helmut Jarausch
2010-01-20 16:26:39 UTC
We can do this by tagging the set's atoms as "optional". (In reply to comment #0) > It would be nice if there were an option to tell emerge to re-emerge > anything that can be done (not depending on those packages which cannot > be re-emerged currently) Isn't that what --keep-going does? I've used it for this in the past. (In reply to comment #2) > Isn't that what --keep-going does? I've used it for this in the past. No, not exactly. What's really needed is a way to cope better with unsatisfied dependencies, as requested in bug 328343. |