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).
Yup. Upon reflection the whole script can be replaced by: emerge -uvD --changed-use --color=n --with-bdeps=y --quiet-build --buildpkgonly --keep-going world | col -bx | mutt -s "world update" y...@example.com That will give you a decent report of what is new, build binary packages, do it in parallel, and not recompute dependencies for every package. Rich
