The dependencies recorded in an src.rpm are only valid for the environment
(including any cli-switches) it was generated in. It's entirely possible to end
up with something quite different on a spec reparse, which is what happens on
any build.
As for pkg-config deps, I see this in the spec, which makes me wonder:
```
# .........
# BuildRequires: pkgconfig(systemd)
# BuildRequires: selinux-policy-devel
```
I can't reproduce any pkgconfig deps appearing in the build, and I can't
imagine rpm hallucinating them up either (this is certainly not AI
:sweat_smile: ). I suggest you double check your findings.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2690#issuecomment-1746412779
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2690/1746412...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
