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 3CB351381F4 for ; Sat, 8 Dec 2012 20:11:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 66E5321C092; Sat, 8 Dec 2012 20:11:15 +0000 (UTC) Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8A09321C01F for ; Sat, 8 Dec 2012 20:09:36 +0000 (UTC) Received: by mail-we0-f181.google.com with SMTP id t11so665495wey.40 for ; Sat, 08 Dec 2012 12:09:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:x-mailer:mime-version:content-type :content-transfer-encoding; bh=2alZAEiqBRRKYZlNNc6ln5+ZYIKDlaq2VKUjGndC6Cs=; b=nvIiG2fTZmblLm24lkOTQoOv02jcv6RMC7gx9Np+HBcqTY6sLdkY0ZmlIBL0BKWj4w ROhZGbRfl/8PgI7VxLWJVjIwa72ZrEvKwF/tQJZg1xPZu45un0Q6HBf4cakG1bYk+T0J Dy028j08bYPV4HnjKocFDG6CJxM9cYTZ7lSHI9DnbYsdu2D2g7DlM6NiLFK+DwT747Ic pMqO8qTC6OIUFMOlQ5WgnHlLk7VBNaY+3bagQMCYzmENM00w4dgvwZ4BebxhvkUdXzzy jL3nMGJ7TUOHVl2ZSIvF0HTRljosD1Tl0oYcKHTx03WukeK41CsKp5O9pu7FsYEp893M LOtA== Received: by 10.216.209.223 with SMTP id s73mr830674weo.30.1354997374932; Sat, 08 Dec 2012 12:09:34 -0800 (PST) Received: from khamul.example.com (196-215-209-117.dynamic.isadsl.co.za. [196.215.209.117]) by mx.google.com with ESMTPS id bd7sm3993137wib.8.2012.12.08.12.09.32 (version=SSLv3 cipher=OTHER); Sat, 08 Dec 2012 12:09:33 -0800 (PST) Date: Sat, 8 Dec 2012 22:06:16 +0200 From: Alan McKinnon To: gentoo-user@lists.gentoo.org Cc: emailgrant@gmail.com Subject: Re: [gentoo-user] System maintenance procedure? Message-ID: <20121208220616.44fb92ae@khamul.example.com> In-Reply-To: References: <20121205120550.2bc346bf@khamul.example.com> Organization: Internet Solutions X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) 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-Transfer-Encoding: 7bit X-Archives-Salt: 024140e3-0ed2-4420-8717-e6c7e131c310 X-Archives-Hash: 8fd27dc5111dfd3a03b96f21262929b2 On Fri, 7 Dec 2012 16:56:18 -0800 Grant wrote: > > > My unattended daily system maintenance procedure is like this: > > > > > > layman -S > > > emerge --sync > > > emerge -pvDuN world > > > emerge -pv --depclean > > > eclean -p distfiles > > > eclean -p packages > > > > > > And then attended like this: > > > > > > > > > revdep-rebuild > > > etc-update > > > elogv > > > emerge --depclean > > > eclean distfiles > > > eclean packages > > > > > > Am I missing any good stuff? > > > > > > - Grant > > > > > > I'd tweak the order of your attended run: > > > > emerge -DuN world > > emerge @preserved-rebuild > > emerge --depclean > > revdep-rebuild > > > > > > The logic is: > > > > Rebuild busted packages that portage already knows about > > (@preserved-rebuild), then get rid of oudated packages and finally > > revdep-rebuild to fix anything that --depclean broke. > > > > @preserved-rebuild is getting very good at what it does lately > > (supported in all recent portage version including stable IIRC), as > > is --depclean, so revdep-rebuild seldom finds anything to do these > > days. > > > > -- > > Alan McKinnon > > If revdep-rebuild does everything that @preserved-rebuild does and > more, why run @preserved-rebuild at all? @preserved-rebuild does it correctly, does not break your system and does not leave it in an indeterminate state while you spend hours trying to figure out what went on. revdep-rebuild does all those things (and also gets around to fixing broken libs while taking it's own sweet time to do it). So they are not really the same thing at all. Basically, portage removes old .so files when doing upgrades. If the so-name changes, packages using that file are now broken. revdep-rebuild was a phase 1 effort to repair that damage after the fact, and it was good at that. @preserved-rebuild is a feature in portage that won't remove old .so files until the last binary linking to it is removed. IOW, things still work meanwhile. It's analogous to the Unix style of deleting files - if you app still has a handle to a file and the file is deleted, your app does not notice the difference as from it's POV the delete has not happened yet -- Alan McKinnon alan.mckinnon@gmail.com