Example of Dependency Resolution Gone Wrong

view full story

http://forums.fedoraforum.org – Here in this thread is an example of dependency resolution gone wrong: The poster installed MATE, decided later to remove it, only to see files in place before MATE was installed targeted for removal. The question, then, is this: If a dependency resolver is clever enough to know what it needs to add to an installation, why isn't it clever enough to know what to ignore when it is being deleted? If packages it requires are already present prior to the install, it should not blithely assume they are safe to resume. Why doesn't it track and remember what it installed, and remove only that? (HowTos)