forked from
anil.recoil.org/monopam-myspace
My aggregated monorepo of OCaml code, automaintained
Merge branch 'better-website' of /cache/jons-agent/workspace/work/better-website
+17
-16
+2
-2
doc-pages/batch.mld
+2
-2
doc-pages/batch.mld
···
18
18
opam repositories within a profile, keyed by commit SHAs.
19
19
20
20
Sits near the top of the dependency hierarchy, depending on
21
-
{!day11-opam-build}, {!page-solution}, {!day11-lib}, {!day11-layer},
22
-
and {!day11-exec}.
21
+
{!page-opam_build}, {!page-solution}, {!page-lib}, {!page-layer},
22
+
and {!page-exec}.
23
23
24
24
{1 Modules}
25
25
+2
-2
doc-pages/jtw.mld
+2
-2
doc-pages/jtw.mld
···
13
13
index generation, dynamic_cmis.json creation, and container script
14
14
generation.
15
15
16
-
Depends on {!day11-opam-build}, {!day11-container}, {!day11-doc},
17
-
{!day11-layer}, and {!day11-solver}.
16
+
Depends on {!page-opam_build}, {!page-container}, {!page-doc},
17
+
{!page-layer}, and {!page-solver}.
18
18
19
19
{1 Modules}
20
20
+1
-1
doc-pages/layer.mld
+1
-1
doc-pages/layer.mld
···
19
19
eviction. {!Day11_layer.Symlinks} maintains per-identifier tracking
20
20
symlinks for layer discovery.
21
21
22
-
Depends on {!day11-exec} for subprocess and sudo access. Has no opam
22
+
Depends on {!page-exec} for subprocess and sudo access. Has no opam
23
23
or package-domain knowledge — domain-specific metadata lives in
24
24
sidecar files owned by higher libraries.
25
25
+2
-2
doc-pages/opam_build.mld
+2
-2
doc-pages/opam_build.mld
···
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
-
Depends on {!day11-runner}, {!day11-opam-layer}, {!day11-solver} (via
20
-
solver_pool), {!day11-opam}, {!page-solution}, and the lower layer and
19
+
Depends on {!page-runner}, {!page-opam_layer}, {!page-solver} (via
20
+
solver_pool), {!page-opam}, {!page-solution}, and the lower layer and
21
21
container libraries.
22
22
23
23
{1 Modules}
+3
-3
doc-pages/opam_layer.mld
+3
-3
doc-pages/opam_layer.mld
···
1
1
{0 day11-opam-layer}
2
2
3
3
Opam-flavoured layer types that give domain meaning to the generic
4
-
{!day11-layer} storage. {!Day11_opam_layer.Build} is the recursive DAG node type: each
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
-
Depends on {!day11-layer}, {!day11-exec}, and {!page-solution}. This
18
-
library defines the types that {!day11-opam-build} and {!day11-doc}
17
+
Depends on {!page-layer}, {!page-exec}, and {!page-solution}. This
18
+
library defines the types that {!page-opam_build} and {!page-doc}
19
19
operate on.
20
20
21
21
{1 Modules}
+2
-2
doc-pages/runner.mld
+2
-2
doc-pages/runner.mld
···
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
-
Depends on {!day11-layer} for storage and stacking, {!day11-container}
15
-
for overlayfs mounts and runc execution, and {!day11-exec} for
14
+
Depends on {!page-layer} for storage and stacking, {!page-container}
15
+
for overlayfs mounts and runc execution, and {!page-exec} for
16
16
subprocess primitives.
17
17
18
18
{1 Modules}
+1
-1
doc-pages/solver.mld
+1
-1
doc-pages/solver.mld
···
11
11
invalidation. {!Day11_solver.Dot_solution} renders dependency graphs as Graphviz
12
12
DOT files for debugging.
13
13
14
-
Depends on {!page-solution} for solution types and {!day11-opam} for the
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}
+1
-1
doc/universe.mli
+1
-1
doc/universe.mli
···
23
23
(** [write_package_refs ~pkg_html_dir ~universe_hashes] writes
24
24
[universes.json] into the package's HTML directory listing which
25
25
universes it references. Moves atomically with the package docs
26
-
during {!Atomic_publish}. *)
26
+
during publication (see {!Day11_exec.Atomic_swap}). *)
27
27
28
28
val collect_referenced :
29
29
html_dir:Fpath.t -> string list
+1
-1
opam_build/build_layer.mli
+1
-1
opam_build/build_layer.mli
+2
-1
opam_layer/build_meta.mli
+2
-1
opam_layer/build_meta.mli
···
3
3
Lives next to {!Day11_layer.Meta} as [build.json] in the
4
4
layer directory. The presence of this file marks a layer as the
5
5
output of an opam package build (as opposed to e.g. a doc layer,
6
-
see {!Doc_meta}, or a future layer kind that doesn't yet exist).
6
+
see {!Day11_doc.Doc_meta}, or a future layer kind that doesn't
7
+
yet exist).
7
8
8
9
The opam-specific information is kept here so that
9
10
{!Day11_layer.Meta} can stay generic and reusable across