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