On 10/16/25 1:41 PM, Iñaki Ucar wrote:
TL;DR: how do packages like pyproject-srpm-macros and the like end up in the default buildroot of different versions of Fedora (official, therefore Koji), EPEL, but also Copr chroots? Is there any documentation about this or could somebody guide me in this process?
Hi,
The correct way to add an SRPM macros package to the default buildroot is to add Requires to redhat-rpm-config. redhat-rpm-config is installed by default in the Fedora mock chroot, on both Koji and Copr and mock on your local system and pulled in by the Fedora packaging stack and available for use locally with fedpkg srpm. If you have macros that are packaged in EPEL and need to be in the default EPEL buildroot, you can also add Requires to the epel-rpm-macros package.
I'm planning an %R_meta macro, similar to %gometa, but for this to work, as you know, the default buildroot must have it in the first place via some R-srpm-macros (which currently does not exist).
I would suggest you consider refactoring your macros so they don't need to be installed at SRPM parse time. After taking over maintenance of the forge and go macros which use the %foometa approach that dynamically sets a bunch of global macros in lua which the packager then uses to fill out the specfile preamble, I am starting to realize that this approach is more trouble than it's worth.
Best, Maxwell -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
