On Wed, Mar 11, 2020 at 06:52:12AM -0700, Troy Dawson wrote:
On Wed, Mar 11, 2020 at 1:25 AM Petr Pisar <ppisar(a)redhat.com>
wrote:
>
> I can only see a small ambiguity regarding build-only packages that are
> filtered out of the module. I believe the rule about the module names should
> not apply for these filtered packages.
>
If they are filtered out of the module, then end users cannot see
and/or use them.
If that is the case, they are fair game for EPEL, and I believe (but
haven't checked) that packagers already should be able to request
them.
I thought so.
Is there a particular package you know about that I could check?
There can barely be any now because there are no modules in EPEL yet. And you
cannot see any of the filtered packages in RHEL because they are not
distributed to repositories (except the few -devel modules).
> But that leads me to a question about -devel modules. RHEL
delivers some
> -devel modules in a CRB repository. These -devel modules consists of the
> filtered packages. Is EPEL going to mimic these -devel modules, or not?
>
Can you give an example of a -devel package in CRB that is from a
package that is filtered from a module?
RHEL-8.1.1:
# dnf module list | grep -e -devel
mariadb-devel 10.3 MariaDB Module
virt-devel rhel Virtualization
module
virt-devel rhel Virtualization
module
E.g. virt-devel:rhel:8010020190916153839 contains
qemu-kvm-tests-15:2.12.0-88.module+el8.1.0+4233+bc44be3f.x86_64 package.
RHEL-8.2 Beta brings python38-devel:3.8 module.
-- Petr