On Tue, Nov 05, 2019 at 03:17:28PM -0500, Stephen Gallagher wrote: > 4. Documentation of how to create a module stream is comprehensive but > daunting. There is a lot of available information, but what is really > lacking is a basic walkthrough for converting a single package to a > module stream. It's not just that the documentaiton is daunting. The _steps_ are daunting. It's not an easy process even for simple cases. [...] > 12. Packaging a module requires writing both a spec file and a > modulemd YAML file, which increases the total amount of work I need to > do. [5] I think having this live in a different repo in a whole different dist-git namespace is a barrier. I'm not sure how to make this easier, but it definitely multiplies the confusion and complexity for me. In retrospect, I'd rather have a module definition file live in some "main" package for each module. And I also think we're missing a lot of the automation that came as requirements out of the "Prototype Phase". https://fedoraproject.org/wiki/Objectives/Fedora_Modularization,_Prototype_Phase -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ 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
