On Thu, Sep 10, 2020 at 01:50:55PM +0100, Joe Orton wrote: > maintain the non-modular packages. We are not going to promise to > commit time and resources to maintain the non-modular packages. Joe, here's a part I hope you can help me understand better. Modularity isn't an entirely new packaging technology. It's simply a layer on top of RPM. Modules are made out of RPMs, and by design, their specfiles are exactly the same as RPMs which happen to be grouped into modules. I understand that it's nice to have exactly one workflow, but it doesn't seem like it's actually all that much extra effort on top of what you already have to do to maintain the module to make a non-modular build. Is this something where triggering the non-modular builds in the same way you build the module would make a difference? Or is there something else that I'm not seeing? -- 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
