Bug 290461

I repeated my own "user mistake" of bug 212703 again, trying to remove packages 
that had no obvious use for me.  Through strange and unlikely dependency 
relationships this also removed packages vitally needed by the user.

While the fix applied to close bug 212703 indeed is a worthy improvement (popup 
at apply time notifying users of what dependencies were found) it still doesn't 
address the follow-on need - allowing the user to interpret what those 
dependencies *mean*.

In this case I tried to remove nautilus-cd-burner, as I will not be burning CDs 
on this Linux running in a VMware machine.  Unfortunately this also removes 
gnome-session, throwing you into twm on next restart.

Your average user is going to be SOL after their mistake at removing something 
unneeded from the system.  


How reproducible:
Every time as below.

Steps to Reproduce:
1. start up "Add/Remove software"  aka pirut
2. Select "Desktop Environments", "Gnome Desktop Environment", and then
     click on "Optional packages"
3. Scroll down to "nautilus-cd-burner - Easy to use CD burning for Gnome"
     and uncheck the checkbox to request uninstall
4. Click "Close", and then click "Apply"
5. Click "Continue" to the confirm removal of "nautilus-cd-burner"
6. Click "Continue" to "Dependencies Added" dialog displaying list 
     "Removing for dependencies" list containing 'gnome-media', 
     'gnome-session', 'gnome-volume-manager'
7. Restart session or reboot, then re-diaper self
 
Actual results:
The desktop has disappeared, offering the user only the twm with xterm, clock, 
and firefox windows.  No menus, menubars, no pretty buttons to push to get 
everything back.

Expected results:
Either
  * general warning that deleting components can have bad results 
      and have you backed up your system lately?
  * warnings plus some (easy) way to lookup what those dependencies 
      _mean_.  Such as bug 227362 mentions.
  * specific warning that deleting heartbeat will cause irreversable
      brain damage

As per the discussion in the previous bug 212703, I understand that this seems 
an unbounded process, as in "when is it important enough?" to mention.  

Perhaps the simplest essential parameter is this - when would removing a 
package totally disable the average (Windows?) user from using their system 
and/or restoring back to its previous state, given average capabilites to do so.

This is indeed 'merely' a usability problem.  One with disastrous consequences 
though...

Additional info:
/var/log/yum.log is a lifesaver!