On Thu, May 22, 2014 at 3:54 AM, Marc Joliet <mar...@gmx.de> wrote: > I think nowadays one would prefer --keep-going, which automatically resumes on > failure (and recomputes the dependency tree!), and prints a list of failed > packages when it's finished. However its output is more verbose than just "ok" > and "failed" (it'll print the build.log if it's only one package, IIRC).
Hmm, after using this script for some time I found a problem with this approach. If you use --buildpkgonly and ---keep-going then emerge won't build a single thing if anything in the list is missing a build-time dependency. The script I posted will try to emerge everything individually so at least some of the packages will be compiled. That seems like a bug in --buildpkgonly. If you use it with --keep-going it should at least compile the packages that aren't missing build-time options. I'll file that as a bug if it isn't already there... Rich
