libmodulemd v2 is a rewrite of v1 without backwards compatibility. Since v1 is being deprecated, MBS should migrate to using v2 when possible to meet with the current standards.
Here is the user guide for libmodulemd v2: https://sgallagh.fedorapeople.org/docs/libmodulemd/2.0/modulemd-2.0-Modulemd.html
I really wanted to use a v2.0 feature but it turns out MBS does not support it yet. This caused me to file this bug: https://pagure.io/fedora-docs/modularity/issue/54
What's the ETA on this?
@mbooth we will be migrating to libmodulemd v2 within the next couple of weeks, but we have not scheduled adding the new features that were added to the spec.
We are quite busy with other commitments, but at least if MBS is migrated to libmodulemd v2, then it allows community members to submit PRs to support the new features in the spec if it's needed sooner than we can deliver this.
The PR for migration to libmodulemd v2 has been already merged. I'm marking this as done.
I think we need smaller cards for tracking particular libmodulemd v2 features we want to implement in MBS.
closing.
Metadata Update from @jkaluza: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
The PR for migration to libmodulemd v2 has been already merged. I'm marking this as done. I think we need smaller cards for tracking particular libmodulemd v2 features we want to implement in MBS.
I filed a separate bug for my favourite most-wanted feature: https://pagure.io/fm-orchestrator/issue/1267
Login to comment on this ticket.