public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A Theoretical install Question
Date: Wed, 23 May 2007 02:57:31 +0200	[thread overview]
Message-ID: <200705230257.31965.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <46538EFB.2030702@exceedtech.net>

On Mittwoch, 23. Mai 2007, Dale wrote:
> Hemmann, Volker Armin wrote:
> > On Mittwoch, 23. Mai 2007, burlingk@cv63.navy.mil wrote:
> >> I think that I will probably be better off doing a stage three
> >> install, then doing an 'emerge -euD world' or similar before
> >> moving on from there.  After that, I can just make sure to watch
> >> the FAQ's and walkthroughs when I install Xorg to make sure that
> >> I do it right.  ^_^
> >
> > why?  there is no need to do that. emerge -u --newuse world would be much
> > more 'interessting'. Btw, an deep world update ruined most of my
> > weekend... don't do --deep if you don't have to.
>
> Funny, I sync every few days or so and always do a emerge -uvD world.  I
> have less problems with that than just doing a -u world.
>
> Maybe it is when you do things consistantly that keeps things going
>well

and are you doing revdep-rebuilt afterwards?

Last time gwenviev and kipi stuff broke, krita broke and some other stuff. 
Krita did not emerge because of some changed symbols, so I had to reemerge 
koffice-libs - something revdep-rebuild did not catch. It catches changed 
versions, but if a lib is recompiled because of an -r update and there are 
symbol problems, revdep will not see them... 
I had to rebuild kdepim and a lot of other stuff, just because of that -D 
update. It sucks to have to revdep-rebuild a douzend packages. It suckes even 
more when half of them fail because of some symbols and you have to reemerge 
three or four additional libs, so you can't just let it run unattended...

In my years of gentoo, -D always caused problems and was almost never worth 
the trouble.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-05-23  1:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  0:13 [gentoo-user] A Theoretical install Question burlingk
2007-05-23  0:21 ` Bo Ørsted Andresen
2007-05-23  8:25   ` Neil Bothwick
2007-05-23  0:25 ` Hemmann, Volker Armin
2007-05-23  0:46   ` Dale
2007-05-23  0:57     ` Hemmann, Volker Armin [this message]
2007-05-23  2:37       ` Dale
2007-05-23  8:22       ` Neil Bothwick
  -- strict thread matches above, loose matches on Subject: below --
2007-05-23  1:40 burlingk
2007-05-22  7:42 burlingk
2007-05-22  8:18 ` Neil Bothwick
2007-05-22  7:13 burlingk
2007-05-22  7:26 ` Dan Farrell
2007-05-22  6:47 burlingk
2007-05-22  7:02 ` Hemmann, Volker Armin
2007-05-22  5:13 burlingk
2007-05-22  4:55 burlingk
2007-05-22  4:06 burlingk
2007-05-22  4:30 ` Iain Buchanan
2007-05-22  5:01 ` Naga
2007-05-22  5:23   ` Dale
2007-05-22  5:39   ` Iain Buchanan
2007-05-22  6:30     ` Naga
2007-05-22 13:03       ` Bo Ørsted Andresen
2007-05-22  6:34 ` Hemmann, Volker Armin
2007-05-22 15:27   ` Dan Farrell

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=200705230257.31965.volker.armin.hemmann@tu-clausthal.de \
    --to=volker.armin.hemmann@tu-clausthal.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