From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Use Flags and Updating
Date: Fri, 23 May 2014 05:22:02 -0400 [thread overview]
Message-ID: <CAGfcS_kSoLcaVjv_JKh14ePnJ2_K9Uf=3q0uUuxShuOugLfxTQ@mail.gmail.com> (raw)
In-Reply-To: <20140522095448.76d13462@marcec>
On Thu, May 22, 2014 at 3:54 AM, Marc Joliet <marcec@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"
you@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
next prev parent reply other threads:[~2014-05-23 9:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 11:37 [gentoo-user] Use Flags and Updating Hunter Jozwiak
2014-05-20 11:43 ` Alexander Kapshuk
2014-05-20 11:40 ` Hunter Jozwiak
2014-05-20 11:49 ` Alexander Kapshuk
2014-05-20 19:13 ` Matti Nykyri
2014-05-21 13:49 ` Alexander Kapshuk
2014-05-22 2:10 ` ny6p01
2014-05-22 3:11 ` Rich Freeman
2014-05-22 7:54 ` Marc Joliet
2014-05-23 9:22 ` Rich Freeman [this message]
2014-06-06 10:44 ` Rich Freeman
2014-06-06 23:45 ` Alan McKinnon
2014-05-22 9:37 ` Neil Bothwick
2014-05-22 12:00 ` J. Roeleveld
2014-05-20 20:56 ` yac
2014-05-21 13:55 ` Alexander Kapshuk
2014-05-21 16:37 ` Francesco Turco
2014-05-20 11:47 ` Stephan Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGfcS_kSoLcaVjv_JKh14ePnJ2_K9Uf=3q0uUuxShuOugLfxTQ@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox