+2 -2

day11/doc-pages/batch.mld

reviewed

··· 15 15 human-readable summary. 16 16 17 17 Sits near the top of the dependency hierarchy, depending on 18 18 - {!day11-opam-build}, {!page-solution}, {!day11-lib}, {!day11-layer}, 19 19 - and {!day11-exec}. 18 18 + {!page-opam_build}, {!page-solution}, {!page-lib}, {!page-layer}, 19 19 + and {!page-exec}. 20 20 21 21 {1 Modules} 22 22

+2 -2

day11/doc-pages/jtw.mld

reviewed

··· 13 13 index generation, dynamic_cmis.json creation, and container script 14 14 generation. 15 15 16 16 - Depends on {!day11-opam-build}, {!day11-container}, {!day11-doc}, 17 17 - {!day11-layer}, and {!day11-solver}. 16 16 + Depends on {!page-opam_build}, {!page-container}, {!page-doc}, 17 17 + {!page-layer}, and {!page-solver}. 18 18 19 19 {1 Modules} 20 20

+1 -1

day11/doc-pages/layer.mld

reviewed

··· 14 14 a cheap mtime-based sentinel for LRU eviction. {!Day11_layer.Symlinks} maintains 15 15 per-identifier tracking symlinks for layer discovery. 16 16 17 17 - Depends on {!day11-exec} for subprocess and sudo access. Has no opam 17 17 + Depends on {!page-exec} for subprocess and sudo access. Has no opam 18 18 or package-domain knowledge — domain-specific metadata lives in 19 19 sidecar files owned by higher libraries. 20 20

+2 -2

day11/doc-pages/opam_build.mld

reviewed

··· 16 16 for investigating failed builds. {!Day11_opam_build.Patches} manages per-package patch 17 17 files that modify builds before execution. 18 18 19 19 - Depends on {!day11-runner}, {!day11-opam-layer}, {!day11-solver} (via 20 20 - solver_pool), {!day11-opam}, {!page-solution}, and the lower layer and 19 19 + Depends on {!page-runner}, {!page-opam_layer}, {!page-solver} (via 20 20 + solver_pool), {!page-opam}, {!page-solution}, and the lower layer and 21 21 container libraries. 22 22 23 23 {1 Modules}

+3 -3

day11/doc-pages/opam_layer.mld

reviewed

··· 1 1 {0 day11-opam-layer} 2 2 3 3 Opam-flavoured layer types that give domain meaning to the generic 4 4 - {!day11-layer} storage. {!Day11_opam_layer.Build} is the recursive DAG node type: each 4 4 + {!page-layer} storage. {!Day11_opam_layer.Build} is the recursive DAG node type: each 5 5 node carries a content-addressed hash, a package, direct dependency 6 6 nodes, and a universe identifier. {!Day11_opam_layer.Tool} aggregates multiple build 7 7 nodes into a single tool layer (e.g. odoc + deps). {!Day11_opam_layer.Build_meta} ··· 14 14 synthetic opam switch-state files so the container sees stacked deps 15 15 as installed. 16 16 17 17 - Depends on {!day11-layer}, {!day11-exec}, and {!page-solution}. This 18 18 - library defines the types that {!day11-opam-build} and {!day11-doc} 17 17 + Depends on {!page-layer}, {!page-exec}, and {!page-solution}. This 18 18 + library defines the types that {!page-opam_build} and {!page-doc} 19 19 operate on. 20 20 21 21 {1 Modules}

+2 -2

day11/doc-pages/runner.mld

reviewed

··· 11 11 variables, bind mounts, commands — are injected by the caller through 12 12 the [prep_upper] callback and the {!Day11_container.Oci_spec.t}. 13 13 14 14 - Depends on {!day11-layer} for storage and stacking, {!day11-container} 15 15 - for overlayfs mounts and runc execution, and {!day11-exec} for 14 14 + Depends on {!page-layer} for storage and stacking, {!page-container} 15 15 + for overlayfs mounts and runc execution, and {!page-exec} for 16 16 subprocess primitives. 17 17 18 18 {1 Modules}

+1 -1

day11/doc-pages/solver.mld

reviewed

··· 11 11 invalidation. {!Day11_solver.Dot_solution} renders dependency graphs as Graphviz 12 12 DOT files for debugging. 13 13 14 14 - Depends on {!page-solution} for solution types and {!day11-opam} for the 14 14 + Depends on {!page-solution} for solution types and {!page-opam} for the 15 15 git-backed package index. 16 16 17 17 {1 Modules}