----- Original Message ---- > From: Alex Schuster <wo...@wonkology.org> > To: gentoo-user@lists.gentoo.org > BRM writes: > > > > If you keep your world file (/var/lib/portage/world) tidy, simply > > > > deleting all lines with KDE3 packages and running emerge -a -- > > > > depclean will take care of it. > > > > You *do* keep your world file tidy, don't you? :P > > > That would be the easiest method. If you use the kde-meta package > > > like I do, just remove the one for KDE 3 and let --depclean do its > > > thing. It should get all of it. > > I actually don't touch the world file, and just do the 'emerge world > > -vuDNa' for updates. From my POV, that is emerge/Portage's job - not > > mine. > I'd also leave the world file alone, and emerge -C the packages I want > removed.
Yep, that's what I do. > > Aside from that, I'm not sure I have ever really run "emerge > > --depclean", but I also rarely uninstall anything, but don't install > > things left or right to try out either, so typically upgrades are all > > I need to do. > > Having just done a compiler upgrade, I can say that there are roughly > > 1100 packages (emerge -eav) in world that were recompiled. > > I was just contemplating - KDE4 is stable, and I don't see myself > > running KDE3 again; so why keep it around. If 'emerge world -vuDNa' > > will remove it when it gets pushed off the main trunk, then that's > > probably fine with me - since that seems to not be very far out now. > > If not, then I definitely want to remove it now as there is no other > > reason for keeping it around. > KDE3 is no longer in the portage tree, it's in the kde-sunset overlay. > > World updates do not remove things, you need to use emerge --depclean for > this. It will probably want to remove a lot when you never depcleaned > before, so be sure to check. Put the stuff you want to keep in your world > file with emerge -n, then depclean the rest. I guess it will remove your > whole KDE3 that is no longer in portage. If you like to keep it, add the > kde-sunset overlay with laymanl, and maybe emerge kde-base/kde-meta:3.5. Thanks. That's what I needed to know. > > That's the only issue. My only concern is software (e.g. KDevelop) that > > may not have been updated to KDE4 yet. (Not a fan of KDevelop3; > > waiting to see how KDevelop4 is going to shape up.) > The KDE4 version is in the kde overlay, but I do not know if it is usable > already. For now, I'll wait. I mostly use vim; and having done a lot of Windows stuff for work I am familiar with VS. While there are a lot of things I don't like about VS, nothing else seems to quite compare. KDevelop3 at least drove me nuts; and Eclipse just doesn't do well when you're not programming in Java - I have yet to get CDT to work, though I've mostly tried on Windows. QtCreator seems to be on the right track, though it's still quite early. I'm interested to see how KDevelop4 is going to turn out, but I'll certainly wait for it to reach the mainline tree. Thanks for the info. Ben
