Red Hat Bugzilla – Bug 491483
yum groupremove "KDE (K Desktop Environment)" removes GNOME components
Last modified: 2009-09-24 18:21:10 EDT
While doing a:
yum groupremove "KDE (K Desktop Environment)"
essential and additional GNOME components are removed, too:
gnome and kde have overlapping components, that's a fact of life these days.
Sorry, but 'yum groupremove' simply isn't smart enough these days to do what you expect... which is (I assume): remove kde, but leave anything in other groups (like gnome-desktop) alone.
One workaround is to:
yum groupremove kde-desktop
yum groupinstall gnome-desktop
to restore stuff.
I tried groupremoving KDE in the current rawhide, and it will remove, among OpenOffice and many other things, both kdm *and* gdm. I'd say it is a little too easy fort the user to end up high and dry. Can the dependencies at least be changed so that a login manager remains? Is there a situation where groupremove is actually usable?
yum remove kdebase kdelibs
practically achieves the goal of removing KDE without killing GNOME/OpenOffice/the login manager. The dependency culprits included in the KDE group seem to be
OpenOffice depends on dejavu-sans-fonts (why?) and gdm depends on polkit-gnome.
yum groupremove doesn't do what you think it does. It is NOT the inverse of groupinstall. There is no inverse of groupinstall.
What does uninstalling a collection from PackageKit-gnome do? I tried to look at the PackageKit yum backend code but I'm not familiar with the yum Python API. If the 'uninstall collection' operation in PackageKit-gnome amounts to a groupremove, I think that is a problem. I just saw a new post on fedoraforum by a newbie who had hosed his system by uninstalling KDE. I don't know how exactly he did the uninstalling, though.