ocaml-builder/test/solver/ at main · gazagnaire.org/ocaml-builder · Tangled

gazagnaire.org / ocaml-builder

0

OCI-oriented build engine

0

ocaml-builder / test / solver

4 files

at main

Thomas Gazagnaire builder, oci: split network-free packages out of the engine 5w ago

builder, oci: split network-free packages out of the engine opam resolves packages whole, so depending on any sub-library of builder or oci pulled the package's entire dependency set: runc, seatbelt and sqlite from the builder engine, and the requests/TLS/HTTP registry client from oci. A consumer that needs only the build model or the local OCI layer cache inherited the whole execution and network surface. Extract the network-free cores into their own packages so they can be consumed without that surface: oci-layer (spec, local store, layer build), builder-spec (spec, plan, runtime, backend), builder-graph (the build DAG) and builder-opam (the opam binary-layer cache and solver). The engine and registry client now depend on these.

1 month ago

builder: fork the opam solver into builder.solver Split the opam_cache library so the core stays solver-agnostic and opam-format-free: builder.opam_cache is now just Cache + Command + Runtime.wrap (the injected-solve substitution decorator), depending only on nox-opam. The opam-0install solver and the turn-key wiring move to a new builder.solver library (Builder_solver: solve, layer_hashes, applicable_depexts, and wrap, formerly Runtime.wrap_opam), which owns the opam-0install/opam-format dependency. This lets a consumer with its own solver (oi) use the cache and inject its solve through the seam, without linking a second solver; and it gives resolution for other package managers a home to grow into later. Runtime.wrap's on_built now hands the resolved native prefix_dir to the caller so the solver lib needs no path helpers. Tests split to match: builder_solver's solve/wrap tests live in test/solver, the core fake-solve decorator tests in test/opam_cache, sharing fake_runtime via test/helpers.

1 month ago

test_builder_solver.ml

builder: key opam PKG steps by deferred closure resolution A RUN opam install step is keyed on the dependency closure opam would install, but that closure depends on the opam repo inside the build rootfs -- which only exists once the prior layers materialise it. Keying on the command alone is unsound (two different repos give two different closures under one key) and keying on the closure was impossible without a rootfs. Resolve both by deferring the key to when the parent is materialised. Runtime.prepare_run gains an optional ~root (the materialised parent rootfs); the engine's exec_op passes the parent it has already built, so the opam decorator resolves the closure against the image's own repo -- the only sound source -- and keys the step on the identity of that closure's layers (opam-layers:<solve_hash>). Two images that install the same closure now share the step and its layers; the run closure restores the pre-resolved layers when cached and runs opam only on a miss. When the rootfs is absent or the command is not a recognised install, the step falls back to a command digest. The pre-build plan cannot key a PKG step until its parent is built: it marks the step (and the chain after it) Build_graph.Deferred when the parent is not cached, and materialises the cached parent to resolve the key otherwise.

1 month ago

test_builder_solver.mli

builder: fork the opam solver into builder.solver Split the opam_cache library so the core stays solver-agnostic and opam-format-free: builder.opam_cache is now just Cache + Command + Runtime.wrap (the injected-solve substitution decorator), depending only on nox-opam. The opam-0install solver and the turn-key wiring move to a new builder.solver library (Builder_solver: solve, layer_hashes, applicable_depexts, and wrap, formerly Runtime.wrap_opam), which owns the opam-0install/opam-format dependency. This lets a consumer with its own solver (oi) use the cache and inject its solve through the seam, without linking a second solver; and it gives resolution for other package managers a home to grow into later. Runtime.wrap's on_built now hands the resolved native prefix_dir to the caller so the solver lib needs no path helpers. Tests split to match: builder_solver's solve/wrap tests live in test/solver, the core fake-solve decorator tests in test/opam_cache, sharing fake_runtime via test/helpers.

1 month ago