public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Update or Install again? Testing vs. stable?
Date: Thu, 14 Sep 2006 15:40:59 +0200	[thread overview]
Message-ID: <200609141541.05133.bo.andresen@zlin.dk> (raw)
In-Reply-To: <7573e9640609132203y30cd0d90m1e7cb1ef6c7265d0@mail.gmail.com>

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

On Thursday 14 September 2006 07:03, Richard Fish wrote:
> 2. Remove ~amd64 from keywords, and basically follow the gcc upgrade
> guide, since you probably need to udpate to gcc 4.1 anyway.
>
> Advantages:
> - It's relatively easy to see what things are going to be downgraded,
> so you can decide what needs to be added to package.keywords.

One warning that should be given regarding any downgrade is that downgrading 
glibc is going to hose any system! Since the newest glibc in portage is 
stable at the moment this isn't currently an issue but still for future 
reference the warning should be given.

Further I may add that I recently went through a downgrade from ~x86 to x86 on 
a desktop system and since I had been using ggc-4.1.1 for almost 3 months I 
decided not to use revdep-rebuild rather than emerge -e world.

The only real problem I experienced was the dev-libs/expat downgrade from 
2.0.0 to 1.95.8. revdep-rebuild doesn't have a clue about the order in which 
to recompile all the packages that break by this so if I hadn't been able to 
figure that out the revdep-rebuild method would definitely have taken a lot 
longer than emerge -e world (because most builds failed until the correct 
packages had been remerged in the correct order). I would, however, expect 
that it would be quite painless if emerge -e world was performed.

Of course given the bugs that are still open on bug #140707 as has been 
discussed on this list during the last couple of weeks you should expect that 
a few packages will require ~x86 keywording until they are stabilised.

Having said all this a agree with Richard about this question.

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-09-14 13:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14  3:33 [gentoo-user] Update or Install again? Testing vs. stable? Alan E. Davis
2006-09-14  5:03 ` Richard Fish
2006-09-14 13:40   ` Bo Ørsted Andresen [this message]
     [not found]     ` <450A3FAF.3070002@qrypto.org>
2006-09-15  7:27       ` Bo Ørsted Andresen
2006-09-15  9:39         ` Rumen Yotov
  -- strict thread matches above, loose matches on Subject: below --
2006-09-14  3:34 Alan E. Davis

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=200609141541.05133.bo.andresen@zlin.dk \
    --to=bo.andresen@zlin.dk \
    --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