Summary: | portage should merge the next ebuild when one ebuild fails | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Benjamin Schulz <schulz.benjamin> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | flash3001, m.debruijne, radek |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 51411 | ||
Bug Blocks: |
Description
Benjamin Schulz
2004-05-16 05:02:07 UTC
Often I Update everything with emerge -Upv world (Since it will take time to update, it is practical to do it only when one has the time to leave the computer alone for a whole day) Sometimes packages fail emerging. It would be great when portage notices the failure, proceeds with the next package (when there are no depencies with the fauled one) and then informs me after the emerge that some packages could not be installed because of the failure of some packages. When I want to see the errors for bugreporting I can emerge the affected ones again. That is not a problem. But it would be great if the new KDE were kompiled when I come back in the evenning and that I have to restart the whole emerge excluding one small and stupid package that has failed. I'm longing for this for really long time, now... |