Dear all, 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? I've seen that they are required in redhat-rpm-config, so it's fair to assume that one should open a PR there to begin with. But then I have seen that e.g. Copr has different versions of this package compared to e.g. Koji, right?
Longer explanation: I would like to submit a self-contained change to bring R macros to the 21st century, make use of dynamic buildrequires for R packages and so on, so that the R packaging experience is on par with other languages. 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 did not find any piece of documentation describing such a procedure, but virtually all the other languages have their <you_name_it>-srpm-macros added there, so I assume there are a number of people here that may help me navigate this. Thanks in advance, -- Iñaki Úcar
-- _______________________________________________ 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
