Extract the mariadb component as a fab unit #6

New issue

Open

opened 2026-09-27 06:05:35 -03:00 by marcos-mendez · 0 comments

marcos-mendez commented

2026-09-27 06:05:35 -03:00

(Migrated from github.com)

The mariadb overlay, conf script and plan fragment live in the shared common
tree, where every appliance shares one history and one gate, and where a change
for one product touches the repository the others build from.

bt-layer records units in the layer manifest and subtracts them by name as
of 2026-09-27, which was the prerequisite handbook decision 0010 set. This is
the first real migration under it.

Closes when the component is its own repository as a unit (plan, overlay/,
an executable conf, a version, tests, a gate), the mariadb layer is
rebuilt from it, and equivalence is proved the way the 0010 experiment proved
it: a repeated control build to establish the noise floor, the package list
identical, every differing file explained, nothing attributable to the unit
form. The published layer is d5220c56 on parent core 7acf2c53 and is not
replaced until the comparison is clean.

The mariadb overlay, conf script and plan fragment live in the shared `common` tree, where every appliance shares one history and one gate, and where a change for one product touches the repository the others build from. `bt-layer` records `units` in the layer manifest and subtracts them by name as of 2026-09-27, which was the prerequisite handbook decision 0010 set. This is the first real migration under it. Closes when the component is its own repository as a unit (`plan`, `overlay/`, an executable `conf`, a `version`, tests, a gate), the `mariadb` layer is rebuilt from it, and equivalence is proved the way the 0010 experiment proved it: a repeated control build to establish the noise floor, the package list identical, every differing file explained, nothing attributable to the unit form. The published layer is `d5220c56` on parent core `7acf2c53` and is not replaced until the comparison is clean.