In general, I like the proposal, while it probably has some gaps, e.g. how the code will be organized in dist git.
And another specific concern is: "I recommend abusing a distribution release package (e.g. fedora-release) which is in a default installation:". I think it would probably make sense to separate this into independent package to ease the management (and possibly to opt out from this feature? Not sure about this)
Vít
Dne 13. 06. 23 v 18:32 Petr Pisar napsal(a):
Hello,
as it seems that module build infrastructure isn't getting any better, as modular YUM repositories are going to be deconfigured https://fedoraproject.org/wiki/Changes/No_default_fedora-repos-modular, there is a time to look at different ways how to package alternative content.
There are few aproaches, like compat packages, or full namespacing (Python). Yet modularity had some unique features, especially retaining nonmangled package names and other RPM dependencies.
I spent some time thinking how to approximate the nice features with current state of RPM, Koji, and DNF and come up with this approach https://ppisar.fedorapeople.org/postmodular/. The linked approach achieves it at the expense of dedicated build targets and an inability to introduce completely new modules (as opposite to new streams of existing modules) after releasing an installation media.
Comments are welcome.
-- Petr
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue