On 12/01/11 17:47, John Andersen wrote:
On 1/11/2011 2:27 PM, Tejas Guruswamy wrote:
This is because rpmorphan only considers rpm "Requires:" and not "Recommends:". So rpmorphan may consider packages orphaned which YaST2 considers needed.
Regards, Tejas
Why would Yast treat recommends as required?
Why would a packager recommend 32 bit libs for an x86_64 bit package only] to have them sit unused?
No one said YaST treats recommends like requires? There are several levels of RPM dependencies in SUSE. Requires: designates a package that is abolutely necessary to even start the program. Installed by default by YaST. Cannot be removed without removing the base package. Recommends: designates a package that is necessary to use one of the program's basic features. Installed by default by YasT. Can be removed without removing the base package. Suggests: designates a package that adds extra optional features to the program. Not installed by default. Can be removed without removing the base package. So in general, you want recommended packages, which is why YaST installs them. If there are excess recommends from a package, it's specified by the packager, it's not YaST's fault for following instructions. If you are sure that a dependency isn't needed, file a bug against the package asking to move the Recommends: to a Suggests:. Also, if you uninstall a package through yast or zypper, it adds a "SoftLock" and doesn't install it again unless absolutely necessary. However rpmorphan doesn't do this - it uses rpm directly - which is why you see YaST trying to undo rpmorphan's actions. All these reasons mean rpmorphan doesn't work quite as expected on openSUSE. If you really want to continue using it, try creating the list of orphans with rpmorpan, then removing them with zypper - this will ensure they don't get reinstalled unless specifically asked for. try rpmorphan | xargs sudo zypper rm Regards, Tejas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org