dmnks left a comment (rpm-software-management/rpm#3691)
Thinking about it more, glibc is involved in actually *running* an executable,
which is something that rpm itself is trying to do here (to run the shell
interpreter).
So in that sense, as soon as rpm needs to run a program during the transaction
(such as a scriptlet) in the target chroot, that's where glibc comes into play
as a dependency already, and thus becomes an implicit `Requires(pre)` of the
package.
I'm not sure about the details here but my guess is that glibc is simply
considered such a fundamental piece of a working (Linux) system that it's just
assumed to get pulled in by the shell (without any dep loops).
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3691#issuecomment-2770366092
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3691/2770366...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
https://lists.rpm.org/mailman/listinfo/rpm-maint
