Summary: | sys-apps/portage: after packages are skipped by emerge --keep-going -e @system, there's no way to automatically resume skipped packages afterwards | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Pacho Ramos <pacho> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra, esqualante, sam |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 373807 |
Description
Pacho Ramos
2009-04-03 22:14:35 UTC
Yes, there is no way to automatically resume skipped packages. Maybe something based on timestamps could work well. Resume list change may happen due to dependency check on resume, which may be inhibited by --resume --nodeps combo. And though I did not yet have chance to check, this also has chance to prevent unexpected list reordering and skips (also good side - I suspect you probably could write arbitrary merge sequence in /var/cache/edb/mtimedb without worrying about list invalidity). |