package opam-monorepo

  1. Overview
  2. Docs
Assemble and manage fully vendored Dune repositories

Install

Dune Dependency

Authors

Maintainers

Sources

opam-monorepo-0.3.2.tbz
sha256=01fd23a751b2270b3c46668a9a58c4bf4739297f10c9f2e6ac3a5d0309136d5c
sha512=ea94a8c115a3da027d56f6942d6e41dfa65fa1da222dc94b669444e54aa65072e6a3e14a806d130bc7ba7943cc01ba949574849ae7af763751033af6f93eaf81

doc/concepts.html

Concepts

An opam-monorepo project uses 3 components in the source tree:

  • a set of opam files containing specifications about the dependencies (for example, a dependency on lwt >= 4.0.0)
  • a lock file (with extension .opam.locked) containing references to exact dependencies (for example, lwt = 4.2.1) and how to get them (URLs, hashes, etc.). It also contains information about transitive dependencies, not just the ones mentioned in opam files.
  • a duniverse folder containing the sources for all the packages mentioned in the lock file

The two important commands are:

  • opam monorepo lock, which will read the opam file and compute a solution using the opam repository and the opam solver. It will create or update the lock file with this solution.
  • opam monorepo pull will read the lock file, download the dependencies, and unpack them into the duniverse/ folder.
OCaml

Innovation. Community. Security.