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 9D2E81381F4 for ; Sat, 8 Dec 2012 21:09:13 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 678D221C092; Sat, 8 Dec 2012 21:08:59 +0000 (UTC) Received: from mail-ea0-f181.google.com (mail-ea0-f181.google.com [209.85.215.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A46F3E05FA for ; Sat, 8 Dec 2012 21:07:29 +0000 (UTC) Received: by mail-ea0-f181.google.com with SMTP id k14so617143eaa.40 for ; Sat, 08 Dec 2012 13:07:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=H0YKfRqAMPYVcD1u3aOe2DakCs8wP/AoCHdPL3JCftQ=; b=LiIUiEUrCidgWrdMVgm+9MybzDCKGW/ANVF5Vkul//Num71LuafoAMaL4BGOO5UEfb K9VUvBn99KVvzH2yVXeZDVXCcUYg7xpg4tO7/JTrJtsywDNypLhjkMtUhrBprqL/RBDQ nbYa+ZRrbalmGXsLDII4IS93tJEkkCnIA3q88S+tb+WiSscUCSV4KkrZvk61uBzoCsbS omiBSpoVRNbLSdbdLKyXdLSEJP+KxvCH1wFFFR6SgCDr3N2lrMVAAhypDHXjjcoGxkvz sKmbGoBYOHbRZu01vNrZ6xqRWcS5OwqBXEU4nDDWxDSx9Gc/SeANF+eeKkgBC/SRH+Um 41IQ== 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 Received: by 10.14.214.132 with SMTP id c4mr31598809eep.18.1355000848233; Sat, 08 Dec 2012 13:07:28 -0800 (PST) Received: by 10.223.158.68 with HTTP; Sat, 8 Dec 2012 13:07:28 -0800 (PST) In-Reply-To: <20121208220616.44fb92ae@khamul.example.com> References: <20121205120550.2bc346bf@khamul.example.com> <20121208220616.44fb92ae@khamul.example.com> Date: Sat, 8 Dec 2012 13:07:28 -0800 Message-ID: Subject: Re: [gentoo-user] System maintenance procedure? From: Grant To: Gentoo mailing list Content-Type: multipart/alternative; boundary=047d7b621df83ab5e304d05db8a4 X-Archives-Salt: afa24b7f-3281-4f1a-8b7f-3f998e5c106b X-Archives-Hash: e232a5d3bb5a550983397eb60c78d512 --047d7b621df83ab5e304d05db8a4 Content-Type: text/plain; charset=ISO-8859-1 > > > 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. I'm not saying they're the same, I'm saying it looks like @preserved-rebuild does a subset of the things revdep-rebuild does. Why run @preserved-rebuild followed by revdep-rebuild if the end result is the same as running revdep-rebuild? I'm sure I'm missing something here but I don't know what it is. - Grant > 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 --047d7b621df83ab5e304d05db8a4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > > > The logic is:
> > >
> > > Rebuild bu= sted packages that portage already knows about
> > > (@preserve= d-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 ver= sion including stable IIRC), as
> > > is --depclean, so revdep-= rebuild seldom finds anything to do these
> > > days.
> > >
> > > --
> > &g= t; Alan McKinnon
> >
> > If revdep-rebuild does everythin= g that @preserved-rebuild does and
> > more, why run @preserved-re= build at all?
>
> @preserved-rebuild does it correctly, does not break your syst= em and
> does not leave it in an indeterminate state while you spend = hours
> trying to figure out what went on.
>
> revdep-reb= uild 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.

I'm not sayi= ng they're the same, I'm saying it looks like @preserved-rebuild do= es a subset of the things revdep-rebuild does. =A0Why run=A0@preserved-rebu= ild followed by revdep-rebuild if the end result is the same as running rev= dep-rebuild? =A0I'm sure I'm missing something here but I don't= know what it is.

- Grant


> Basically, portage removes ol= d .so files when doing upgrades. If the
> so-name changes, packages u= sing 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 l= ast binary linking to it is removed. IOW, things still
> work meanwhi= le. 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


--047d7b621df83ab5e304d05db8a4--