I am missing a feature in emerge: When I want to compile some/all ebuilds it creates a list of the ebuilds and begins merging. When one package fails for some reason, the complete emerge-process is stopped though other following packages may be independent from that error. e.g. "emerge a52dec gftp" -> a52dec fails, gftp could emerge but emerge is stopped. -> One failing package cancelles the rest so that some of the packages are up to date and some are not... that's quite annoying (especially when you want to emerge (-e) world) and you have to check that by hand (difficult and really uncomfortable with 700 installed packages). Sure, you may use "--resume --skipfirst", but that's not a good solution, because you have to watch for your ebuild-process and order the system to continue merging by hand. (or write something senseless like "emerge -eD world || emerge --resume --skipfirst || emerge --resume --skipfirst || emerge --resume --skipfirst....") What do you think about the idea to implement an "--ignore-errors" switch to let emerge continue it's list until no ebuild is left and print a summary of failed ebuilds. Example: ----------- ~ # emerge -e --ignore-errors world <emerge begins it's work> ... <emerge fails somewhere on package "foo"> <emerge continues automatically with the next package> ... <emerge finishes> Summary: The following package(s) failed: "foo-bar/foo" ~ # ----------- I think that this is really usefull, please consider it. Reproducible: Always Steps to Reproduce: 1. 2. 3.
*** This bug has been marked as a duplicate of 12768 ***
