| 1 |
Daniel da Veiga wrote: |
| 2 |
> I'm watching this topic with curiosity, I have switched to ~x86 |
| 3 |
> recently and after it all (and a few debugging) I have all my packages |
| 4 |
> testing now, but have not switched to the new GCC for fear of things |
| 5 |
> breaking beyound my knowledge on how to fix it. So, if people start |
| 6 |
> replying saying things are stable with the new GCC I might switch to |
| 7 |
> it completely and wait a few days before the "emerge -e system && |
| 8 |
> emerge -e world" completes. |
| 9 |
> |
| 10 |
I was running stable with a lot of testing unmasked. Then upgraded |
| 11 |
to gcc-4.1.1 with an immediate emerge -s && emerge -e, which went |
| 12 |
mostly smooth. |
| 13 |
|
| 14 |
Then decided to go ~x86 for the system. That is where the pain was, |
| 15 |
particularly expat which caused most of kde/gnome to need to be |
| 16 |
upgraded. Unfortunately a lot of the tools to do the rebuild also |
| 17 |
depended on expat. So it was update a few packages, rebuild a tool, |
| 18 |
update a few more packages, ... Lesson learned is when upgrading |
| 19 |
to expat-2, immediately take the hours needed to do the |
| 20 |
revdep-rebuild (in all honesty, I didn't see the ewarn message |
| 21 |
because I was upgrading 448 packages). It really would have been |
| 22 |
nice if the expat-2 emerge package died after giving the instructions |
| 23 |
to revdep-rebuild... |
| 24 |
|
| 25 |
So far (5 days) the system has been real nice, no problems. KDE |
| 26 |
appears (subjective) faster (with USE=kdehiddenvisibility). So +1 on |
| 27 |
upgrading a ~x86 to gcc-4.1.1. |
| 28 |
|
| 29 |
For those considering stable to testing, the main changes are |
| 30 |
pam-logon/shadow (unmerge pam-logon), coldplug/udev (unmerge |
| 31 |
coldplug), expat (revdep-rebuild), ocaml (dependent packages must |
| 32 |
be manually rebuilt afterwards). |
| 33 |
|
| 34 |
HTH, |
| 35 |
Roy |
| 36 |
-- |
| 37 |
gentoo-user@g.o mailing list |
Archives