package opam-monorepo
Assemble and manage fully vendored Dune repositories
Install
Dune Dependency
Authors
Maintainers
Sources
opam-monorepo-0.3.0.tbz
sha256=a1ef33a349e38bc25ee248dd03366f14388eaff17e172d324e870334af0e428f
sha512=c7bcf724086d124a0ace9875aa050f49eb3c8b14b5ad5232b221cd074c4acd91637623ec446c976c229e144bc61eb661121849902a0b454f4df03601f769396c
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 lockfile (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, which contains the sources for all the packages mentioned in the lockfile
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 lockfile with this solution.opam monorepo pull
will read the lockfile, download the dependencies, and unpack them into theduniverse/
folder.
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>