Hi, Following some long discussions on rpm's and mock issue tracker¹, I wrote the following to permit using BuildRequires, computed from the content of the packaged archive: https://github.com/nim-nim/mock-install https://copr.fedorainfracloud.org/coprs/nim/mock-install/ https://bugzilla.redhat.com/show_bug.cgi?id=1629371 A review would be appreciated Usage is pretty simple: %<-- BuildRequires: mock-install […] %prep […] # Do something to compute yourbr1 … yourbrX mock-install yourbr1 … yourbrX %<-- I intend to integrate it in the next version of Fedora Go packaging macros. I'm told the Java guys already do something similar within javapackages-tools, but it's hidden inside java-specific python packaging code, you can't really use it standalone for other kinds of packaging. Of course the utility is written in Go, so will only build on arches that support Go but *shrug* at this point I don't care, feel free to write something better if you want. The Go code is small and trivial. Regards, ¹ https://github.com/rpm-software-management/mock/issues/160 -- Nicolas Mailhot _______________________________________________ packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/packaging@xxxxxxxxxxxxxxxxxxxxxxx
