2011/8/22 Space Cake <spaceca...@gmail.com>: > 2011-08-19 14:54 keltezéssel, Nikos Chantziaras írta: >> On 08/19/2011 03:02 PM, Space Cake wrote: >>> hi, >>> >>> after playing a lot with desktop environment first I've decided to move >>> from kde to gnome because kde is too "shine" and eat too much and >>> contains a lot of feature which I don't really need.. gnome is good but >>> still too fat.... so finally I've found Xfce which is perfect for my >>> needs... :) >>> >>> my question is what is the easiest way to get rid of kde/gnome stuff? is >>> this enough to change my useflags to -kde and -gnome? Is there any list >>> what I can safely unmerge in this case? >> >> You change your profile. You can see your current profile with: >> >> eselect profile list >> >> For KDE you would use "default/linux/amd64/10.0/desktop/kde" and for >> Gnome "default/linux/amd64/10.0/desktop/gnome". >> >> For anything else, use "default/linux/amd64/10.0/desktop". Then do a: >> >> emerge -auDN --with-bdeps=y world >> emerge -a --depclean >> >> If KDE/Gnome stuff still remains after that, use: >> >> emerge -pv --depclean <package> >> >> to see what's pulling-in <package>. >> >> > So, what if I have changed the flags to -kde and -gnome, and I also ran > depclean, also used the script provided by some kind member of the list > and I still have all the kde gnome stuff on my system? Do I need some > list of packages should I unmerge? Should I simple unmerge packages > kde-base/* and so on and run revdep-rebuild after this? Is this a > working approach?
I just cleaned off KDE (and PulseAudio, as it happens) from my system Saturday night/sunday morning. I wasn't using the KDE profile. Here are the steps I followed: 1) Remove all 'kde' and 'qt' USE flags from make.conf. (I didn't have to remove qt, but I preferred to switch over to package-specific support for it, as needed, rather than global) 2) emerge --depclean (pretend first, then add anything I *knew* I didn't want to lose to @world, then pretend again, until there wasn't anything that would be removed I wasn't comfortable with) 3) If there were any KDE packages left, emerge -pPv on them, to find what was pulling them in. "emerge --deselect" the packages that were pulling the KDE packages in. (Sometimes, this would involve supplying an alternative. For example, I had to emerge Awesome before it would remove knotify.) 4) Jump back to step 2, unless I couldn't get a package to disappear with --depclean. 5) revdep-rebuild (in my case, only a Jack library was busted) 6) emerge --deep --newuse --keep-going world && emerge --sync && emerge --update --deep --newuse --keep-going world # This part, I left running overnight. It succeeded, to my surprise. I did have a couple recursive-dependency-like situations. For example, KDE has a policykit agent, which depends on polkit. The policykit agent wouldn't go away; emerge -pPv said polkit was pulling it in, and said that the agent was what was pulling polkit in. In those situations, I found I had to --unmerge a piece of the dependency loop in order for emerge to allow it to go away or get replaced. In the polkit case, I removed the KDE agent. I also had to remove a few packages I do occasionally use, because they were pulling in Qt or KDE. In particular, I --deselect'd calibre. I've still got qt libs on my system, though, because I use Luminance-HDR a *lot*. I found it surprisingly painless. Note, I went through most of these steps with X *NOT* running; I switched to a terminal and stopped kdm before really going past step 2. -- :wq
