[CentOS-devel] Reasoning behind RHEL8 packages without corresponding -devel?

Nico Kadel-Garcia

nkadel at gmail.com
Sun Sep 1 02:41:53 UTC 2019

On Tue, Aug 27, 2019 at 10:02 PM Neal Gompa <ngompa13 at gmail.com> wrote:
> On Sun, Aug 25, 2019 at 8:19 AM Kaleb Keithley <kkeithle at redhat.com> wrote:
> >
> > On Sun, Aug 25, 2019 at 12:05 AM Anthony Alba <ascanio.alba7 at gmail.com> wrote:
> >>
> >> (Of course, we should be asking RH... but nevertheless)
> >>
> >> EPEL 8 has several issues regarding packages without corresponding
> >> -devel. E.g., libXvMC, libbluray.
> >
> >
> > AIUI, certain -devel packages land in the CodeReady repo. But these two in particular are not actually in the CodeReady repo.
> >
> > It appears it was not an oversight. See https://bugzilla.redhat.com/show_bug.cgi?id=1713421. (Some comments are private.)
> >
> > And FWIW, you can always get the src RPMs and build them yourself to get the -devel packages. Generally I'd agree that you should not have to do this, but based on the private comments in that BZ I'd guess that that may be your only option at this time.
> >
> That whole bug report is private. I can't read it, nor do I imagine
> anyone else can.
> I hope that CentOS 8 won't follow RHEL 8 in this manner, and we'll
> have all the -devel subpackages available and integrated into the
> repos or something. Otherwise, it's going to be extremely painful to
> build on top without rebuilding things to get access to components
> that were already built...

I can't read that bug report, and I have a personal Red Hat account
with my RHEL 8 license. What is the point of bug report not even your
customers can read?

The latest release of "mock" and "mock-core-configs" from the git
repos work reasonably well with RHEL 8. I've published RPM wrappers
for them, at https://github.com/nkadel/mockrepo . Getting the RHEL 8
keys means declaring a subscription key manually right now.

More information about the CentOS-devel mailing list