modulemd

#59 Filters should be arch-specific
Opened by ralph. Modified

Open
Close Issue

Today, the modulemd spec allows for a filter to be specified; it lists binary subpackages. These are meant to be stripped from the module before distribution.

To meet some needs, we need the filter to be arch-specific. I.e., so that some binary subpackages are stripped out for some architectures, but not for others.

When this first came up, my argument was that this should be controlled by the SPEC files. I still think so.

If that's not an option, the module author can limit what architectures the components are built for, affecting the availability of all binary packages of the component. Although this affects other things as well.

I understand this is not what you're asking for, even though I think the options above solve the majority of uses cases. Changing the filters would be an incompatible change and would require a bump. Does the above work for you or are per-arch filters in modules really necessary?
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.