From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How can I update *every* ebuild?
Date: Wed, 23 Jan 2013 15:21:35 -0600 [thread overview]
Message-ID: <20130123212135.GO30998@server> (raw)
In-Reply-To: <51003E73.2080201@gmail.com>
On Wed, Jan 23, 2013 at 08:48:03PM +0100, Jarry wrote:
> Hi Gentoo-users,
> I always thought the right way to update everything was:
>
> emerge --update --deep --newuse world
> emerge --update --deep --newuse system
>
> When I try the above mentioned, nothing to update is found.
> Yet when I try i.e. "emerge --pretend nasm", I see:
>
> [ebuild U ] dev-lang/nasm-2.10.05 [2.10.01]
>
> So there is apparently update for dev-lang/nasm, yet it was
> not pulled when I tried to update the "world" or "system".
> And who knows for how many other ebuilds there is update
> available...
>
> So how can I update really *every* ebuild?
This alias is in /root/.bashrc:
alias ud='eix-sync && emerge -aDjNuv @world && dispatch-conf && emerge -a --depclean && revdep-rebuild -i && clear && exit'
emerge -aDjNuv @world
a = ask (Yes/No prompt -- don't waste time with --pretend)
D = deep (consider the entire dependency tree of packages)
j = jobs (no number after j means to run as many simultaneously as possible)
N = newuse (pkgs with changed USE flags)
u = update (to the best version available)
v = verbose
@world = world set
"man emerge" would be very enlightening for you...
It's important to sync (eix-sync) before you start, or your local portage tree
won't have any new software; and equally important to check configs
(dispatch-conf), clean out pkgs no longer needed (--depclean), and rebuild any
deps (revdep-rebuild). Don' forget to read news (eselect news read).
Running this ud alias every morning with coffee on no less than 8 Gentoo boxen
on this LAN keeps everything updated, clean, and I'm usually one of the first
to find new bugs. Well, since my test machine running ~amd64 is no longer in
service, there are less bugs. But, still, there are enough bugs in amd64.
Cheers,
Bruce
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
next prev parent reply other threads:[~2013-01-23 21:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 19:48 [gentoo-user] How can I update *every* ebuild? Jarry
2013-01-23 19:52 ` Florian Philipp
2013-01-23 19:53 ` Michael Mol
2013-01-23 20:07 ` Hilco Wijbenga
2013-01-23 20:24 ` Michael Mol
2013-01-24 0:02 ` Dale
2013-01-23 21:21 ` Bruce Hill [this message]
2013-01-23 22:27 ` Neil Bothwick
2013-01-23 23:01 ` Bruce Hill
2013-01-23 23:15 ` Neil Bothwick
2013-01-23 23:37 ` Bruce Hill
2013-01-24 8:32 ` Neil Bothwick
2013-01-24 9:17 ` Dale
2013-01-24 9:27 ` Neil Bothwick
2013-01-24 9:46 ` Dale
2013-01-24 12:37 ` Neil Bothwick
2013-01-24 12:54 ` Jean-Christophe Bach
2013-01-24 13:38 ` Yohan Pereira
2013-01-24 14:04 ` Neil Bothwick
2013-01-24 12:43 ` Kerin Millar
2013-01-24 14:12 ` Trevor D. Manning
2013-01-24 18:17 ` [gentoo-user] " »Q«
2013-01-24 7:21 ` [gentoo-user] " Alan McKinnon
2013-01-24 12:59 ` Kerin Millar
2013-01-24 15:41 ` Stroller
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=20130123212135.GO30998@server \
--to=daddy@happypenguincomputers.com \
--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