On Mon, Jun 13, 2022 at 4:18 PM Chris Adams <linux(a)cmadams.net> wrote:
Once upon a time, Josh Boyer <jwboyer(a)redhat.com> said:
> If the dependency is only needed at build time, which is what CRB
> content is intended for
If that's the intent, then it's not implemented correctly. For example,
there are well over 100 perl modules in CRB 9. They may only be used
_by Red Hat_ in building, but they are not exclusively build-time
packages by a long shot.
If it helps, I've updated my CRB scanner and the results (hopefully
it's accurate) for seeing what EPEL packages depend on CRB packages
(via "dnf rq --whatdepends <crb_package>") for both EL8 and EL9. These
were run against RHEL 8 and 9 repositories with EPEL (so no EPEL
Next). I don't believe it'll catch everything (such as things in
epel-modular), but it could be a decent starting point for review.
Would also be useful to know if this methodology is flawed and
inaccurate.
https://gitlab.com/omenos/crb-depends
--
Mike Rochefort