1 |
...is not so good actually. Certainly not the way I'd want others to |
2 |
experience Gentoo. |
3 |
|
4 |
OK, the ~amd64 upgrade to @system was easy and relatively painless. |
5 |
The documents were fairly clear. There are things to learn, and old |
6 |
friends like rc-update and df look different, but it worked and didn't |
7 |
take long - less than an hour to reboot including editing - so that's |
8 |
good. |
9 |
|
10 |
Unfortunately, simply allowing all environments & apps on the system |
11 |
to go ~amd64 isn't working out as nicely. |
12 |
|
13 |
1) xfce4 had one build failure. I masked it and the build finished. |
14 |
xfce starts and seems to mostly work, but I get no wallpaper and the |
15 |
right click for a menu on the desktop doesn't work. It's usable, but |
16 |
clearly 'not stable'. |
17 |
|
18 |
2) gnome-2.28 simply doesn't build. |
19 |
|
20 |
3) I'm currently left with lots of things in emerge @preserved-rebuild |
21 |
that don't build. emerge -DuN @world is not clean. |
22 |
|
23 |
QUESTION: Assume I'm happy with ~amd64 on @system, but want to build |
24 |
the stable version of gnome or kde. How do I get it? Since gnome-2.26 |
25 |
worked yesterday I tried masking >=gnome-2.28. emerge -DuN gnome. |
26 |
Portage then didn't try to emerge the meta-package but doesn't take |
27 |
all of gnome back to 2.26. There's no point trying kde as gnome pulled |
28 |
in kde components that doesn't build either. Hopefully it's not 'mask |
29 |
every package in gnome by hand'. |
30 |
|
31 |
At this point I'm left with a system that's not clean and to me not |
32 |
terribly useful. Yesterday as stable I built xfce, gnome and kde in |
33 |
under 4 hours and all 3 worked. Today both gnome and xfce aren't right |
34 |
and I don't have kde. Probably this is some matter of learning to hold |
35 |
back portage that I've never done before, rather than unleashing new |
36 |
packages like you do on a stable system. |
37 |
|
38 |
How does one accomplish this? |
39 |
|
40 |
Thanks, |
41 |
Mark |