From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 18C31138631 for ; Wed, 23 Jan 2013 21:21:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2334F21C0EF; Wed, 23 Jan 2013 21:21:41 +0000 (UTC) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8B4F721C020 for ; Wed, 23 Jan 2013 21:21:39 +0000 (UTC) Received: from localhost (66-208-231-133.ubr01a.rte20201.pa.hfc.comcastbusiness.net [66.208.231.133]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0Lufsm-1Uxp7Q3J6u-010BGN; Wed, 23 Jan 2013 16:21:38 -0500 Date: Wed, 23 Jan 2013 15:21:35 -0600 From: Bruce Hill To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How can I update *every* ebuild? Message-ID: <20130123212135.GO30998@server> References: <51003E73.2080201@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51003E73.2080201@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V02:K0:danUQPTEt1rMSxuHJexRNKyzhYICzwYlurLMQTQbCvK 6Lb40vj5jxnafmJDcDa7DoZPC/W62SMQnpJGiqp0ZHwkJHUSAY pnqJaI7ZxwNSg599CYpBSHACpFIoWyr6lv1UmUhL9k+FIlka3d +EPtjzJpjZmF/qXM2L0+KsDZzTETUvYHwyo7mxo+RzgVTEl0F5 //MDiefJSxTzjN0f5krw+stl1/mqPJkDXIiMZK+shYvZyR6cwq ne51ITgVbrkudrptprZUF09a/sWONM4kkW065uVeZ5CaxvP7AB d6I2ed8qVqE7V3Ol5vc8wN4+DkeY9pyxTnJT88FCTax4Vv9c77 EMYCQhOh0NBflMQkhBh8LEfqsAh0NI/LuWCtPwFdX X-Archives-Salt: e215a953-cc7a-48fe-aeac-de762c4e2a62 X-Archives-Hash: ffbf50fc5a35c54acf3dcd16c092e618 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