YUM: Transition of dependencies

A goal of apt and problem that has to overcome Yum is more efficiency in dependancy analysis and manage it according to the situation, for example , I can install a package called "A" that depend of other called "B" and "C" is duty of Yum install B and C (B <-A-> C), then if I want to install other package called "D" and this depends only of B Yum will install only D (D<->B) because B just was installed by A, Just here no problem, neverthless I want via Yum _only_ uninstall "A", this will remove B, C and D but "D" not have some inherency in A, so why Yum uninstall B and D? Yum should simply uninstall A and C and let B and D.

For example 'yum remove alsa-lib' remove Gnome, graphical and X Window system, I know that alsa-lib is a base package but I cannot have Gnome and not have alsa?(Obviously with 'rpm -e --nodeps' could do but it's not the case), other example is 'yum remove NetworkManager' it remove everything that depend on 'libnm_glib.so' library or 'NetworkManager-glib' package as system-config-printer, PackageKit, pidgin, etc. maybe it's necessary to granulate a bit more the packages then yum should to be more efficient.

El sedante de Kappa Omicron Kappa

Disfunctional fraternities or social commite, "La chica llego y subio con un miembro KOK...la vergüenza casi la mata pero no pudo evitar la caminata." WTF, I was watching "Sorority Boys" movie after a very LONG day, curiously young boys and girls living in a frat house called "Kappa Omicron Kappa", ("KOK", say it out loud). maybe is time for change my nickname.