On Thu, 16 Oct 2025 at 21:06, Maxwell G <[email protected]> wrote: > <snip> > > > 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. >
Ok, valuable advice. My current approach is in [1]. I liked the idea of automating a bunch of things, so I wrote [2]. But feedback is very welcome, and particularly what would you do instead of this given your experience. [1] https://github.com/rpm-software-management/R-rpm-macros/pull/2#issuecomment-3411156648 [2] https://github.com/rpm-software-management/R-rpm-macros/blob/8d2386f40cc6a25f248e4d9739af7dc1ae843c79/macros.R-srpm#L22-L71 -- 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
