public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Blumentritt <marc.blumentritt@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: gcc upgrade from 3.x to 4.x, when should I run revdep-rebuild?
Date: Fri, 08 Sep 2006 09:27:24 +0200	[thread overview]
Message-ID: <45011B5C.10401@arcor.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0609071428540.6851@mail.magrittesystems.com>

michael@michaelshiloh.com schrieb:
> I'm upgrading my gcc from 3.x to 4.x. I've done the gcc switching, and
> now I'm
> updating my system.
> 
> The recommended steps are:
> 
>   # emerge -eav system
>   # emerge -eav world
> 
> While emerging my system I received a message suggesting I run
> revdep-rebuild:
> 
>   warning - be sure to run revdep-rebuild now
> 
> My question is, should I run revdep-rebuild right after emerging the
> system,
> or should I wait until after I emerge world? My concern was that in
> between,
> my system is in an unstable intermediate state, and it might be damaged
> by a
> revdep-rebuild in between.

Well, you rebuild world, which includes all packages you would rebuild
with revdep-rebuild. I would run revdep-rebuild after the rebuild of
world, just to be sure. I also recommend to look through the info
outputs of every emerge, if you missed something, e.g. I had messages
like "rebuild against the new library, than it is save to delete the old
one." If you miss this, then you have cruft libs on your system.

Cheers
Marc


-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-09-08  7:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 21:34 [gentoo-user] gcc upgrade from 3.x to 4.x, when should I run revdep-rebuild? michael
2006-09-08  7:27 ` Marc Blumentritt [this message]
2006-09-08 13:00   ` [gentoo-user] " Dale
2006-09-08 19:22     ` Marc Blumentritt
2006-09-08 19:42       ` Dale
2006-09-08 19:38     ` Bo Ørsted Andresen
2006-09-08 21:14       ` Dale
2006-09-08 21:27         ` Richard Fish
     [not found]           ` <450221F1.9070806@vista-express.com>
2006-09-09  2:17             ` Richard Fish
     [not found]             ` <200609090459.16850.bo.andresen@zlin.dk>
2006-09-09  3:33               ` Dale
2006-09-09  3:55                 ` Bo Ørsted Andresen
2006-09-09  4:15                   ` Dale
2006-09-11 21:32                     ` Neil Bothwick
2006-09-12  3:37                       ` Dale
2006-09-12  4:29                         ` Ryan Tandy
2006-09-12  6:04                           ` Dale
2006-09-12  4:13                       ` Bo Ørsted Andresen
2006-09-08 21:53         ` Neil Bothwick
2006-09-08  7:37 ` [gentoo-user] " Richard Fish
2006-09-08  7:54 ` Alan McKinnon
2006-09-08  8:23   ` Richard Fish

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=45011B5C.10401@arcor.de \
    --to=marc.blumentritt@arcor.de \
    --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