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