Le 2019-11-27 08:08, Tom Hughes a écrit :
On 27/11/2019 01:49, Chris wrote:
I kind of like the way nagios-plugins breaks apart it's check_scripts
into many sub-packages, but 50+ subpackages seems a bit extreme... or
is it? It certainly seems like a bit of a nightmare to maintain; it
would be one very large .spec file.
If the subpackages are sufficiently identical you can just use lua
to programatically generate the relevant spec fragment - see lodash
for an example:
That’s also how it is done for go packages and in the proposed fonts
packaging update. Though it is heavier upstream-agnostic lifting, you
may not need this level of abstraction just for 50 packages.
https://pagure.io/fonts-rpm-macros/blob/master/f/templates/rpm/spectemplate-fonts-0-simple.spec
https://pagure.io/go-rpm-macros/blob/master/f/templates/rpm/spectemplate-go-0-source-minimal.spec
It just reads the list of modules from a text file in the distgit repo
and generates the spec fragment for each one.
The clean way to do it is to put the list of things to generate against
in a spec variable, and write the generator logic in a (lua) rpm macro.
That keeps the generation inside the spec instead of moving some package
creation steps outside our the shared and audited build infra.
Regards,
--
Nicolas Mailhot
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
