package opam-monorepo
Assemble and manage fully vendored Dune repositories
Install
Dune Dependency
Authors
Maintainers
Sources
opam-monorepo-0.2.7.tbz
sha256=a6fedc60739f0e7313500e40ed4a7d1ea68483aad9e67e5408e01dbf08224e71
sha512=8de46a58652bc3818a92fc67fe2d39de341abae4f7dc5a096069a49e4267b5629a76ab3453fe32e423dc14da96f40121d883d36d51b7d8c2ce48a97b87b7bc9d
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)"
>