That's because opi depends on package rpm-build, which brings all these deps. The spec mentions: "for rpm building and snap extracting" That seems a bit excessive. On 1/19/24 19:53, Felix Miata wrote:

Should I report a bug? If yes, against TW? SR isn't apparent there. To update opi: # time zypper -v dup ... Computing upgrade... ... The following package is going to be upgraded: opi 3.5.0-1.1 -> 4.3.0-1.1

The following 29 NEW packages are going to be installed: binutils 2.41-1.2 debugedit 5.0-5.6 dwz 0.15-2.6 gcc 13-1.6 gcc13 13.2.1+git8109-1.1 gettext-runtime 0.21.1-2.4 gettext-tools 0.21.1-2.4 glibc-devel 2.38-7.1 libasan8 13.2.1+git8109-1.1 libatomic1 13.2.1+git8109-1.1 libctf-nobfd0 2.41-1.2 libctf0 2.41-1.2 libhwasan0 13.2.1+git8109-1.1 libitm1 13.2.1+git8109-1.1 liblsan0 13.2.1+git8109-1.1 liblzo2-2 2.10-8.4 libtextstyle0 0.21.1-2.4 libtsan2 13.2.1+git8109-1.1 libubsan1 13.2.1+git8109-1.1 libxcrypt-devel 4.4.36-1.4 linux-glibc-devel 6.6-1.1 make 4.4.1-2.5 patch 2.7.6-6.9 python-rpm-macros 20231010.0a1f0d9-1.1 python-rpm-packaging 20210526+a18ca48-1.9 python311-packaging 23.2-1.1 rpm-build 4.18.0-6.2 rpm-build-perl 4.18.0-6.2 squashfs 4.6.1-2.2

1 package to upgrade, 29 new. Overall download size: 1.3 MiB. Already cached: 48.7 MiB. After the operation, additional 188.3 MiB will be used. Continue? [y/n/v/...? shows all options] (y): n #

Why are all these construction packages required in order to do opi package searches? Is this really intended?