package opam-monorepo
Assemble and manage fully vendored Dune repositories
Install
dune-project
Dependency
Authors
Maintainers
Sources
opam-monorepo-0.3.5.tbz
sha256=a87e758690324f0835ddf06bd0f01ca7c7fb1c1d9338375da1fb2243aec19a67
sha512=ad89112cd238838c9b8a0022dbf860c76c78cb393d91363aba5baf46ac5cdb167147ee244d5d818cc26aa7c44378d8e6477d017b0414d46e3576d173c0d5c321
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 theduniverse/
folder.
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>