On Sunday, January 29, 2017 3:32:22 PM CET Dale wrote: > Might I also add, the -t option can reveal what is causing what > sometimes. Also, I'd start with @system first, then work on @world. > Only bad thing is, KDE, if you have it installed, is in @system because > of dependencies, last I checked anyway. That will make @system a lot of > fun itself.
KDE (and theoretically even gnome) can end up poluting @system due to certain USE-flags. If this happens during a big update, try switching to a non-desktop profile. My preferred way to do a big update like this is to temporarily move the "world" file out of harms way. Update @system and then do a depclean. After a year (or more) nearly all packages will need updating, which means you're not loosing much. If you prefer to be able to keep using the machine, starting with a recent stage3 and creating a consistent set of binary packages will make your life a lot simpler as well: 1) Inside a chroot, build all the packages you need (with up-to-date versions) to match your collection of world/world_sets and use-flags. 2) Once you have all the binary packages, temporarily clear out everything but @system 3) Install everything from binary packages (emerge -ek @world) I've managed to easily update an old laptop this way that hadn't been updated for over 2 years without any real issues. -- Joost
