On 2019-10-07, Jaroslav Mracek <jmracek@xxxxxxxxxx> wrote: > I would like to open discussions more widely, because we are talking about > future of software distribution and discussing only particular issue is not > an approach how to delivery solid and stable architecture. > > What issues I have in mind? > 1. Fedora system upgrade (libgit2, axa, bat) > I guess this is about changing platform stream without rebuilding modules. I.e. once relengs create Fedora 32 compose, no modules (except of virtual "platform") can be installed because they require previous platform:31. How it works in classical Fedora? Relengs take Fedora 31 content and copy it into Fedora 32 repository. And suddenly you have packages for Fedora 32. How it could workd in modular Fedora? Relengs take Fedora 31 content including modules and copy it into Fedora 32 repository. Then they take modulemd data and rewrite all modular dependencies from platform:31 to platform:32. Voila, you have modules for Fedora 32. These modulemds should be imported into MBS to be available at build-time. We don't have to rebuild the modules because identical packages can belong to more module builds. -- Petr _______________________________________________ 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
