On Wed, Dec 07, 2022 at 02:23:18PM +0100, Petr Pisar wrote:
Those who should be concerned most are DNF5 developers and relengs producing composes.
There are third party repositories which also publish modular metadata. I know this because in yum.theforeman.org we do this. Do we fall under relengs producing composes?
If you are interested in it, I recommend starting with overview.xml file. It shows a skeleton of the format. It's so small I can quote it here: <index xmlns="http://fedoraproject.org/metadata/moduleindex"; version="" revision=""> <module name=""> <stream name=""> <!-- DNF wants versions and contexts to differ in @summary etc. --> <build version="" context="" static="" arch="" summary="" description=""> <!-- @static defaults to false. --> ... <references comunity="" documentation="" tracker=""/>
Is comunity a typo for community?
A grand plan how to implement and deploy this format is outlined in top-level README.md <https://github.com/fedora-modularity/libmodulemd/blob/main/xml_specs/README.md>. Basically it will be injected into createrepo_c tool to produce the XML data in YUM repositories.
I really like integration into the existing tooling like createrepo_c. That was a massive gap in functionality. The plan is rather light on these details so I'd be interested to see how you plan to expose this functionality.
_______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
