Re: [gentoo-user] Re: How to dump kde gracefully in favor of lxde
On Mon, Feb 20, 2017 at 01:44:02PM +0100, Kai Krakow wrote > You could also try to stop portage from even syncing the KDE components > into the tree. I usually do this for small systems to not give portage > any chance of pulling in unwanted components. As a plus, syncing and > dep calculation should be faster. That would generate error messages. The best solution is to get rid whatever is pulling in KDE. As for blocking stuff to pull in, to quote Frank Sinatra, "I did it m-y-y-y-y-y way". I wrote a script, /etc/portage/cleanup which generates /etc/portage/rsync_excludes on my machines. Note that the groups listed are what I don't use. Your machine(s) will probably have a different set of unnecessary stuff. #!/bin/bash remove() { rm -rf /usr/portage/${1}/ /usr/portage/metadata/md5-cache/${1}/ echo "${1}/" >> /etc/portage/rsync_excludes echo "metadata/md5-cache/${1}/" >> /etc/portage/rsync_excludes } # # Remove rsync_excludes rm /etc/portage/rsync_excludes remove app-emacs remove app-leechcraft remove app-mobilephone remove app-pda remove app-xemacs remove dev-dotnet remove dev-embedded remove dev-haskell remove dev-java remove dev-qt remove dev-ros remove dev-ruby remove java-virtuals remove kde-apps remove kde-base remove kde-frameworks remove kde-misc remove kde-plasma remove lxde-base remove lxqt-base remove mate-base remove mate-extra remove net-p2p remove ros-meta remove sec-policy remove www-apache remove xfce-base remove xfce-extra -- Walter DnesI don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Re: How to dump kde gracefully in favor of lxde
On Monday 20 Feb 2017 15:32:25 Grant Edwards wrote: > On 2017-02-19, Mickwrote: > >> And what pulls in NetworkManager? KDE's power manager with USE=wireless! > > I despise NetworkManager. Over the years, it has been the cause of > countless problems and hours of wasted time. The first I do when > dealing with network problems on *buntu systems is uninstall > NetworkManager. > > > Yes! Madness. What's wrong with good ol' wpa_supplicant and its GUI? > > Which is spelled "emacs /etc/wpa_supplicant.conf I mentioned the GUI in case there were people who preferred it. The CLI equivalent is wpa_cli of course. ;-) -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] Re: How to dump kde gracefully in favor of lxde
"Walter Dnes"writes: [...] > 1) "eselect profile list" and switch to a basic non-KDE profile of your > choice. Moved from: default/linux/amd64/13.0/desktop * to default/linux/amd64/13.0 * > > 2) "emerge gentoolkit" if not already present. > > 3) "cat /var/lib/portage/world" and see what KDE stuff you have. No kde in there > 4) Unmerge (i.e. "emerge --unmerge) obvious KDE-related stuff that you > find in world. got that accomplished and and several more pkgs that were causing blocks > 5) "emerge --depclean" (May not help if you've done "emerge --sync" and > not fully updated). > Nothing gets listed there >The next 3 steps are going to be repeated several times > > 6) "emerge -pv --changed-use --deep --update @world" > > 7) You'll probably see portage try to pull KDE back in. For each lib > "fu-bar/foobar" that portage tries to pull in do "equery d fu-bar/foobar" > and manually unmerge whatever it finds. (Note: gentoolkit provides the > equery tool). > 8) GOTO 6 (until portage stops trying to pull in KDE stuff). I'm still working on this, but wanted to thank you for your input. I like help that has an outline of how to go at something. Very helpful.. and I seem to be close to getting this cleaned up.
[gentoo-user] Re: How to dump kde gracefully in favor of lxde
On 2017-02-19, Mickwrote: >> And what pulls in NetworkManager? KDE's power manager with USE=wireless! I despise NetworkManager. Over the years, it has been the cause of countless problems and hours of wasted time. The first I do when dealing with network problems on *buntu systems is uninstall NetworkManager. > Yes! Madness. What's wrong with good ol' wpa_supplicant and its GUI? Which is spelled "emacs /etc/wpa_supplicant.conf -- Grant Edwards grant.b.edwardsYow! My haircut is totally at traditional! gmail.com
[gentoo-user] Re: How to dump kde gracefully in favor of lxde
Am Sat, 18 Feb 2017 22:05:01 -0500 schrieb "Walter Dnes": > On Sat, Feb 18, 2017 at 04:57:52PM -0500, Harry Putnam wrote > > > Any advice about slick ways of getting fully updated but dumping kde > > on the way. > > *IMPORTANT* KDE is obscene about dependancies. E.g. when a > lightweight pdf-reader was phased out, I looked at various options > including okular. It's an "itty-bitty-little-applet"... that seems to > pull in 90% of KDE as dependancies. If you want to get rid of KDE, > you must be prepared to dump every last little KDE app/applet. It's > an all-or-nothing situation. Sorry. > > 1) "eselect profile list" and switch to a basic non-KDE profile of > your choice. > > 2) "emerge gentoolkit" if not already present. > > 3) "cat /var/lib/portage/world" and see what KDE stuff you have. > > 4) Unmerge (i.e. "emerge --unmerge) obvious KDE-related stuff that you > find in world. > > 5) "emerge --depclean" (May not help if you've done "emerge --sync" > and not fully updated). > >The next 3 steps are going to be repeated several times > > 6) "emerge -pv --changed-use --deep --update @world" > > 7) You'll probably see portage try to pull KDE back in. For each lib > "fu-bar/foobar" that portage tries to pull in do "equery d > fu-bar/foobar" and manually unmerge whatever it finds. (Note: > gentoolkit provides the equery tool). > > 8) GOTO 6 (until portage stops trying to pull in KDE stuff). You could also try to stop portage from even syncing the KDE components into the tree. I usually do this for small systems to not give portage any chance of pulling in unwanted components. As a plus, syncing and dep calculation should be faster. https://wiki.gentoo.org/wiki/Handbook:X86/Portage/CustomTree#Excluding_packages_and_categories -- Regards, Kai Replies to list-only preferred.