public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge @ world -> @preserved-rebuild ->   @preserved-rebuild -> what next?
Date: Sat, 14 Nov 2009 08:37:13 +0000	[thread overview]
Message-ID: <20091114083713.1dc9200a@digimed.co.uk> (raw)
In-Reply-To: <5bdc1c8b0911131706g26e7ac1aq337fb3221581404d@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]

On Fri, 13 Nov 2009 17:06:02 -0800, Mark Knecht wrote:

> > I think it is being over-cautious, which results in packages being
> > rebuilt multiple time unnecessarily, but I's rather give it the
> > chance to fix itself. That said, I've never had a list anything like
> > 50 packages long, but I do update frequently.
> >  
> It wasn't that I had 50 packages in the emerge -DuN @world. That was
> something like 10. It was after that finished and I ran
> @preserved-rebuild that it said 50 packages were effected by something
> it found, but those 50 were all dependent on just one or two packages
> that Alan was suggesting to me are held in the preserved database
> file, or so I think.

I realised it was 50-odd in the rebuild list, but in my experience
multiple runs gradually reduces that number. Maybe portage could be more
intelligent about the order in which it re-emerges these packages, but
running it enough times always works for me.

Removing the registry is potentially risky because you could still have
packages linked to a library that is not managed by portage, and that
will never update. If someone finds a security hole in that library, you
could be in trouble.

"Fixing" the problem by deleting the registry is akin to fixing low oil
pressure in your car by disconnecting the warning light.


-- 
Neil Bothwick

We are THOR of Borg... your RFC compliant mailbox has been assimilated

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-11-14 10:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 14:43 [gentoo-user] emerge @ world -> @preserved-rebuild -> @preserved-rebuild -> what next? Mark Knecht
2009-11-12 14:58 ` Alan McKinnon
2009-11-12 15:14   ` Mark Knecht
2009-11-12 16:19     ` Mark Knecht
2009-11-12 16:28       ` Alan McKinnon
2009-11-12 16:49         ` Mark Knecht
2009-11-13 12:39   ` Neil Bothwick
2009-11-13 18:42     ` Alan McKinnon
2009-11-13 19:46       ` Mark Knecht
2009-11-13 20:57         ` Alan McKinnon
2009-11-13 22:19           ` Mark Knecht
2009-11-13 22:38             ` Neil Bothwick
2009-11-13 23:00               ` Mark Knecht
2009-11-13 23:13                 ` Neil Bothwick
2009-11-14  0:19                   ` Dale
2009-11-14  1:06                   ` Mark Knecht
2009-11-14  8:37                     ` Neil Bothwick [this message]
2009-11-14 19:51                     ` Alan McKinnon
2009-11-14 19:49                   ` Alan McKinnon
2009-11-16  8:58                     ` Erik

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=20091114083713.1dc9200a@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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