Conversation
MuseScore is the only consumer of either recipe, and it no longer resolves mnxdom through muse_deps: src/importexport/mnx fetches mnxdom itself and takes only nlohmann_json and json_schema_validator from here. mnx_w3c existed solely to feed MNX_W3C_SOURCE to the mnxdom recipe. mnxdom now vendors the w3c schema and examples under third_party/w3c-mnx, so there is nothing left to point it at. Both recipes are stale on top of that: mnxdom pins a pre-schema-27 commit, and its patch was obsoleted upstream by mnx-works/mnxdom#57, which picks the bare or namespaced validator target on its own. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Neither of the
mnxdomnormnx_w3crecipes has a consumer. MuseScore is the only app that uses mnxdom, andmusescore/MuseScore#34487 has it take just
nlohmann_jsonandjson_schema_validatorfrom muse_deps while fetching mnxdom itself in-module.As I understand current thinking,
mnxdomis not going to move intomuse_depsuntil MNX has an official spec. This could be many months away. The schema is still revising and mnxdom moves with it. Behindmuse_depseach revision means a recipe bump, a prebuilt/lock cycle, and a submodule pin bump, for a dependency a single MuseScore module uses.mnx_w3cexisted only to feedMNX_W3C_SOURCEto themnxdomrecipe.mnxdomnow vendors the W3C schema and examples underthird_party/w3c-mnx(mnx-works/mnxdom#56, #58), so nothing points at it.Both recipes are also stale.
recipes/mnxdompinse7c947b(2026-02-21,DEP_VERSION 2.1), from before MNX schema 27; MuseScore needs45bf462(v3.1.0). Its0001-link-namespaced-json-schema-validator.patchwas obsoleted upstream by mnx-works/mnxdom#57, which selects the bare or namespaced validator target on its own — the patch no longer applies to any currentmnxdom. Adopting these recipes later would mean rewriting them, not reusing them, so this is a revert-friendly deletion rather than a loss.Scope and checks:
DEP_KIND source, so there are noprebuilt.lockentries and no published archives to retire.cmake -P buildtools/validate.cmake→OK - 54 deps (52 buildable), recipes + prebuilt.lock well-formed.recipes/nlohmann_jsonandrecipes/json_schema_validatorstay; MuseScore now requires both directly.