From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Use Flags and Updating
Date: Thu, 22 May 2014 14:00:47 +0200 [thread overview]
Message-ID: <1551470.P9fhooQK59@andromeda> (raw)
In-Reply-To: <CAGfcS_kb4yB3mzeX60SYHSm0J327LjBE4n7icovMby5L9egnBg@mail.gmail.com>
On Wednesday, May 21, 2014 11:11:02 PM Rich Freeman wrote:
> On Wed, May 21, 2014 at 10:10 PM, <ny6p01@gmail.com> wrote:
> > I run a script that syncs portage, updates @world, depcleans,
> > revdep-rebuild and finally runs dispatch-conf -- about once weekly. Keeps
> > my system in fine trim. :)
>
> This one is a gem - I forget where I saw it (likely planet, but maybe
> it was on a list). Stick it in your crontab. I will warn you that
> sometimes it chokes on its own output and obviously it can't build
> binpkgs for anything more than one step down the dependency tree.
> However, when my weekly chromium build runs at 2AM and I can just
> install it (with -k) the next morning it is a nice thing indeed. You
> still get full control over USE flags/etc, but most of the convenience
> of a binary distro.
>
> #!/bin/sh
>
> LIST=$(mktemp);
>
> emerge -puD --changed-use --color=n --columns --quiet=y --with-bdeps=y
> world | awk '{print $2}' > ${LIST};
>
> for PACKAGE in $(cat ${LIST});
> do
> printf "Building binary package for ${PACKAGE}... "
> emerge -uN --quiet-build --quiet=y --buildpkgonly ${PACKAGE};
> if [[ $? -eq 0 ]];
> then
> echo "ok";
> else
> echo "failed";
> fi
> done
Alternatively, set up a chroot to build the binpackages.
I do that for all my machines at home. That runs weekly.
--
Joost
next prev parent reply other threads:[~2014-05-22 12:01 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
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 [this message]
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=1551470.P9fhooQK59@andromeda \
--to=joost@antarean.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