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                       ^^
[email protected]
662-269-2706 662-205-6424
http://happypenguincomputers.com/

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

Reply via email to