Yum dependency resolving & remove_leaf_only

P J P pj.pandit at yahoo.co.in
Sat Oct 12 20:00:58 UTC 2013


> On Sunday, 13 October 2013 12:50 AM, Reindl Harald <h.reindl at thelounge.net> wrote:
> there is no if and but if a package has a dependency than it has one - period

   Sure, it has dependency. That does not make it an _absolutely_ requirement to have a functional system. Because the dependency relationship could be broken. We already agreed on that, no?  Ex. I try to remove package bluez, and yum prompts me to remove gnome-shell, gthumb, xchat and several other unrelated useful packages.

Does that mean gnome-shell, xchat & gthumb can not function without package bluez? No. It means dependency relationship is broken.

That is why it is okay to let user remove package 'bluez'.  If it breaks something, user can still re-install bluez without much hassle _if & when_ he/she figures out that things aren't working as expected. Otherwise it's good riddance, one unwanted package less.


===
[~ @ 01:00]# yum remove bluez
Loaded plugins: langpacks, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package bluez.x86_64 0:4.101-9.fc19 will be erased
--> Processing Dependency: bluez >= 4.34 for package: pulseaudio-module-bluetooth-3.0-10.fc19.x86_64
--> Processing Dependency: bluez >= 4.42 for package: 1:gnome-bluetooth-3.8.2.1-1.fc19.x86_64
--> Running transaction check
---> Package gnome-bluetooth.x86_64 1:3.8.2.1-1.fc19 will be erased
--> Processing Dependency: gnome-bluetooth(x86-64) >= 3.5.5 for package: gnome-shell-3.8.4-2.fc19.x86_64
--> Processing Dependency: libgnome-bluetooth-applet.so.0()(64bit) for package: gnome-shell-3.8.4-2.fc19.x86_64
---> Package pulseaudio-module-bluetooth.x86_64 0:3.0-10.fc19 will be erased
--> Running transaction check
---> Package gnome-shell.x86_64 0:3.8.4-2.fc19 will be erased
...
===

 I wonder why is gnome-bluetooth required by gnome-shell, it should be the other way round, no?


> there are no soft-depencencies and any hack allow you to remove
> a pakcage which is required by another one and ignore this
> requirement is pretty dumb


   Heh, and leaving users unable to remove unnecessary packages by prompting them to remove 100 unrelated useful packages is not dumb?
 

---
Regards
   -Prasad
http://feedmug.com


More information about the devel mailing list