Like the summary says.. it's about proceeding with the emerge of other
unrelated/unaffected packages after a emerge failure.
when doing things like emerge world -u..or some mass emerge of several
packages.. if by chance some ebuild fails.. emerge will stop and every package
that was listed after the emerge will not be merged.
What I propose is the capability of recording emerge fails(logs), sort out what
packages in the emerge queue list will be affected or not .. emerge the
unaffected, and record in the log the packages that were not merged because of
when the emerge finishes the unaffected packages merge, it could:
warn the user about the failure and:
- show the failure (cat of the log file).
- indicate some file with the failure(log).
*** This bug has been marked as a duplicate of 12768 ***