
Hello, On 2022-02-08 16:48, Martin Wilck wrote:
On Mon, 2022-02-07 at 15:33 +0100, Axel Braun wrote:
... zypper se -i --recommends works similar, and this is OK for a single packages, but is a bit difficult for nested dependencies.
AFAIK neither rpm nor zypper show nested deps. They can't be derived easily. running "zypper in" in a minimal container is probably the safest bet.
To show all directly required dependencies for an already installed RPM package I use # rmp -e --test installed_package Then one has to do that recursively for what was listed to get the transitive closure. In my experience this is the only reliably working way because rpm query commands only show some RPM data. I don't know how to prove if an already installed RPM package is installed because it is required or because it is recommended. Perhaps when "rmp -e --test installed_package" does not list it as required by another package one can conclude it is installed because it is recommended. To show all required dependencies for a not yet installed package I use # zypper in --dry-run package_to_be_installed Kind Regards Johannes Meixner -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5 - 90409 Nuernberg - Germany (HRB 36809, AG Nuernberg) GF: Ivo Totev