Clarify metadata mechanism for submodule-core modules #14

New issue

Open

opened 2026-07-19 05:19:04 +02:00 by michael · 0 comments

michael commented

2026-07-19 05:19:04 +02:00

Owner

Open question: do these repos actually need id/version/tier/type, or only provides (used by adapters to find them)? version/tier/type only seem meaningful for .stpkg-distributed modules with their own release cycle.

Likely needs anagild to properly answer (dependency graph between adapters and provides), so parking this until anagild is operational. Not blocking current fragjan cleanup work.

Related: init.lua metadata block, config/module.conf provides field.

Submodule-core repos (like daw-module-manager itself) are embedded as git submodules and never distributed via .stpkg/registry-index. They currently carry the full daw-modul-* init.lua metadata block (id, version, tier, type, provides) as a stopgap. Open question: do these repos actually need id/version/tier/type, or only provides (used by adapters to find them)? version/tier/type only seem meaningful for .stpkg-distributed modules with their own release cycle. Likely needs anagild to properly answer (dependency graph between adapters and provides), so parking this until anagild is operational. Not blocking current fragjan cleanup work. Related: init.lua metadata block, config/module.conf provides field.

michael added the

coordination/cross-repo

labels

2026-07-19 05:19:04 +02:00