Le mercredi 13 novembre 2019 à 06:43 +0100, Nicolas Mailhot via devel a écrit : > > The native Go component format (also, confusingly, named > module) handles those 3 constrains and won't present any core > difficulty in rpm packaging once it is finished upstream. And, BTW, we added auto-builderequires in rpm 4.15 so you can automate the mapping between well-behaved language component systems and rpm, and individual packagers do not have to care about this mapping in each and every package, when upstream has already made the effort to manage its component versionning. It effectively gives us the same capabilities as modules in rpm proper, in a working reliable way, without all the tech complexity invented module-side. -- 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
