mfile: one env var table under one name — fold vars, vars_lenient and the task env_vars together, merging by name · Issue #3469 · gominimal/minimal · GitHub
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your se
8000
ssion.Dismiss alert
{{ message }}
Repository navigation
mfile: one env var table under one name — fold vars, vars_lenient and the task env_vars together, merging by name #3469
Follows the owner ruling on gominimal/arch#177 (2026-11-16).
Today.
crates/mfile/src/expand.rsSPEC_KEYS has three variable keys: vars (a table), vars_lenient (a list of { name, value } rows) and env_vars (a table). BOX-180 merges vars and vars_lenient by name (merge_vars, VAR_KEYS). env_vars, which task entries use (docs/reference/tasks.md#env_vars), is still replaced wholesale under BOX-064's general rule.
vars_lenient exists only to accept names that are not POSIX-shaped. A TOML table can hold any name Linux accepts, quoted where needed, so one table can hold every variable.
The architecture's rule (gominimal/arch#177).[env_vars] and the env vars a loadout sets merge by variable name at every expansion layer, each type of an extends chain included. Up to and including the entry, the most specific layer wins on a name. A selected loadout only adds names, and a different resolved value fails the expansion with exit 3. The architecture names
8000
no loadout key, so it does not change when this issue lands.
Scope:
One variable table under one name, for every entry type, [defaults], [defaults.<type>], Box Type defaults and loadouts, holding any name Linux accepts. The name must match the Box Spec schema feat(mfile): replace the interim SPEC_KEYS table with the full box.toml schema (BOX-076) #3096 adopts. That schema says env_vars today; if vars is preferred, ask gominimal/arch to rename the box.toml table first.
Retire vars_lenient and whichever of vars and env_vars is not chosen, with a migration path for existing minimal.toml and loadout files.
Retire BOX-184 (a name set twice in one layer), which has no case once a layer has one table. Update spec 29 BOX-048, BOX-064, BOX-167 and BOX-180, docs/reference/minimal-dot-toml.md, docs/reference/loadouts.md and docs/reference/tasks.md.
Owner decisions of 2026-11-16 for this issue: the one table is env_vars, matching the architecture's [env_vars]. vars and vars_lenient retire. A minimal.toml or loadout file that still uses a retired key fails the expansion with exit 3, and the message names the new key. There is no interim acceptance. The plan is a spec 29 amendment first, then two tasks under S5 (#2371): one for mfile, the client expansion and the docs, one for the boxes loadout parser, the wire types and the daemon composer. #3096 and #3467's item 2 wait on both.
Delivered. #3632 amended spec 29: one env_vars table at every layer (BOX-205), the retired keys refused (BOX-206), POSIX names only (BOX-207). The three tasks are merged: T135 #3662, T136 #3691 and T137 #3683. Spec 28's matching edit is #3631 (BCLI).
Activity
agent-137 commentedon Nov 16, 2026
Owner decisions of 2026-11-16 for this issue: the one table is
env_vars, matching the architecture's[env_vars].varsandvars_lenientretire. Aminimal.tomlor loadout file that still uses a retired key fails the expansion with exit 3, and the message names the new key. There is no interim acceptance. The plan is a spec 29 amendment first, then two tasks under S5 (#2371): one formfile, the client expansion and the docs, one for theboxesloadout parser, the wire types and the daemon composer. #3096 and #3467's item 2 wait on both.docs(specs): one env_vars table that merges by name (spec 29) (gomini…
agent-137 commentedon Nov 21, 2026
Delivered. #3632 amended spec 29: one
env_varstable at every layer (BOX-205), the retired keys refused (BOX-206), POSIX names only (BOX-207). The three tasks are merged: T135 #3662, T136 #3691 and T137 #3683. Spec 28's matching edit is #3631 (BCLI).