On Tue, Apr 13, 2010 at 12:30 AM, William Kenworthy <bi...@iinet.net.au> wrote: > On Tue, 2010-04-13 at 09:09 +0200, Alan McKinnon wrote: >> On Monday 12 April 2010 18:33:21 KH wrote: >> > Am 12.04.2010 14:57, schrieb Alan McKinnon: >> > >> >> So, in the rare case of a user who can discipline himself to say within the >> limits you describe, your advice is fine. But that's a theoretical situation >> :-) and the real one is quite different in my experience. >> >> > > This is exactly how I manage a number of gentoo systems - only unmasking > versions I need. Ive actually never done a ~ system :) >
It's an experience. Like you in the past I've keyworded what I needed and it's worked great for 10 years. OK, so I've been pushing forward and finally I'm emerge -e @world clean. xfce still doesn't work right. It's in fact pretty unusable at the moment as it has no menus at all, but it's only a backup environment so I'm going to ignore that for the moment and build KDE which should be done in about 2 hours. Notes about what I think happened here: 1) I missed the message about running perl-cleaner so I had to do that. 2) I had a gcc build that didn't allow the profile to get set so emerge -1 gcc fixed that. 3) After that I tried emerge -e @system, emerge -e @world which failed with more perl issues, but the same package seemed to be part of @system and emerge -e @system was clean. A second pass at emerge -e @world failed the same way. Thinking back to the old days, and I know folks have negative opinions about this, I did emerge -e @system TWICE in a row, and then emerge -e @world worked. Go figure. I'm going to finish KDE and see if it works. If it does then cool, I'll stick with ~amd64. If not I'm deleting the partitions and starting over with stable. I've invested a day and a half in this experiment and my results are not leaving me comfortable. I need to the machine to work so I can use it starting this afternoon. Thanks, Mark Cheers, Mark
