Just got my laptop back up after having been down for awhile and it is in dire need of an upgrade. After syncing, a -uDvp world showed about 100 packages needing upgrading, one of which was gcc, from 3.3 to 3.4. I decided to do it first since most packages seemed dependent on it so headed over to the GCC migration guide and followed the instructions.
I noticed that it said I might have some problems if I used the revdep-rebuild method so I decided to use the emerge -e method instead. Followed the instructions up to the point of issuing an emerge -e and then I realized it would rebuild the 100 packages that would then shortly be upgraded. Or if I did the upgrade first, the emerge -e would recompile the packages I had just upgraded. So, my problem is, how do I avoid the extra 100, unnecessary compiles? I tried "emerge --emptytree --upgrade -p" but it ignored the upgrade option so I can't combine them that way. Should I backup and use the revdep-rebuild method after the upgrade? Would it avoid compiling the packages just upgraded? I seems a possible solution would be to do the upgrade but save a list of the packages to be upgraded. Make a 2nd list of the packages to be recompiled with the --emptytree option. Remove the upgraded packages from the emptytree list and, using some command line involving xargs, recompile the remaining packages in the emptytree list. I apologize for any obtuseness and over-complexity here and I realize, that in the time spent asking the question, I probably could have had the compiles done by now. However the laptop runs hot and I want to avoid the extra stress on it. Any thoughts? Tony -- Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin -- gentoo-user@gentoo.org mailing list
