On Sun, Jun 12, 2022 at 6:50 AM Sérgio Basto <sergio(a)serjux.com> wrote:
On Sun, 2022-06-05 at 00:54 +0200, Neal Gompa wrote:
> Let me start with examples that I get *regularly*: Pagure fails to
> install from EPEL on RHEL/CentOS/Alma/etc. because python3-markdown
> is
> not available. KDE Plasma fails to install because of a mass of
> missing dependencies.
if epel use crb to build some package, crb should be enabled when we
install epel repo, yes , that is my opinion
If the dependency is only needed at build time, which is what CRB
content is intended for, then there is no reason to default to having
CRB enabled because nothing will be installed from CRB anyway. The
issue that people are running into is that EPEL packages have
developed *runtime* dependencies on CRB content. For a subset of
users, that is probably fine. However, if a package needs something
at runtime it would be better to first inquire about putting that
dependency in BaseOS or AppStream rather than just blindly using it
from CRB.
josh