On Fri, 14 Jan 2022 07:02:23 -0500
Josh Boyer <jwboyer(a)redhat.com> wrote:
2) Moving content to CRB in RHEL is not a silver bullet solution in
many scenarios. If it's strictly for build dependencies, CRB works
well. If an EPEL package has a runtime requires on CRB content, that
is less desirable. RHEL CodeReady Linux Builder (CRB) content is
unsupported, not enabled by default, and not intended to be used at
runtime in production. EPEL itself is clearly in the same unsupported
category, but requiring another unsupported repo at runtime may lead
to unintentional surprises for many users.
The EPEL documentation specifically says to enable CRB/PowerTools if
you're using EPEL:
https://docs.fedoraproject.org/en-US/epel/#how_can_i_use_these_extra_pack...
NOTE for RHEL 8 users with certificate subscriptions: EPEL packages
assume that the 'codeready-builder' repository is enabled. You can
do this with:
subscription-manager repos --enable
"codeready-builder-for-rhel-8-$(arch)-rpms"
NOTE for CentOS 8 and CentOS Stream 8 users: EPEL packages assume
that the 'powertools' repository is enabled. You can do this with:
dnf config-manager --set-enabled powertools
Whilst that is for EL-8 I don't see why it would be different for EL-9.
In particular, for interpreted languages like perl there are a large
number of runtime dependencies from EPEL packages to packages in CRB.
Paul.