Legend:
Page
Library
Module
Module type
Parameter
Class
Class type
Source
Page
Library
Module
Module type
Parameter
Class
Class type
Source
base
as a dependency to fix build on macos-arm (#411, @reynir, reported by @gm0stache)opam-monorepo
will always use the pinned repository. (#398, #353, @samoht, @reynir, reported by @emillon)opam monorepo pull
. Loading an switch state might take a few seconds -- replace it with a call to ocamlc --version
to check if the lockfile is compatible with the currently available OCaml compiler (#403, @samoht)dev-repo
field and is being skipped because of it (#341, #362, @kit-ty-kate, @Leonidas-from-XIV)--keep-symlinked-dir
to preserve symlinks in duniverse/
, which can be useful for local development. (#348, #366, @hannesm, @Leonidas-from-XIV)dev-repo
fields to be able to detect more semantically equivalent URLs, this should reduce the risk of build failures due to duplicate code pulled (#118, #365 @TheLortex, @Leonidas-from-XIV)dev-repo
constraints in the opam solver - this allows to resolve more involved version constraints that were failing before (#396, @samoht)compiler
flag from OPAM metadata thus classifying more packages correctly as base packages (#328, @Leonidas-from-XIV)opam monorepo pull
placing package source code directly inside the duniverse directory instead of in a subdirectory of the duniverse directory (#359, @gridbugs)x-opam-monorepo-repositories
(#284, #317, @Leonidas-from-XIV)pull
would crash if the lock file contained no package to vendor (#321, @NathanReb)archive-mirrors
from the global opam configuration into account to allow more local caches (#337, @hannesm)--add-opam-provided
and --opam-provided
to be ignored by the solver. (#314, @NathanReb)--minimal-update
flag to lock
to generate a lockfile with minimum dependency changes from a previous lockfile. (#305, @NathanReb)x-opam-monorepo-*
fields. (#307, @NathanReb)lock
CLI arguments in x-opam-monorepo-cli-args
when generating a lock file. (#309, @NathanReb)opam-provided
packages into pin-depends and duniverse directories anymore, thus stop pulling packages that should be installed via Opam (#302, @Leonidas-from-XIV)x-opam-monorepo-opam-repositories
and x-opam-monorepo-global-opam-vars
to make lock
fully reproducible. (#250, #253, @NathanReb)opam-monorepo
. To control this a new optional Opam file field, x-opam-monorepo-opam-provided
is introduced. Its value is a list of package names that are to be excluded from being pulled (#234, @Leonidas-from-XIV)duniverse/README.md
file to explain the basics of opam-monorepo
in the vendored directory (#272, #274, @Leonidas-from-XIV)--prefer-cross-compile
flag for the solver to select cross-compiling versions of packages when available. This is determined through the presence of the "cross-compile"
tag in the opam metadata.vendor
variable so using OPAM with opam install --deps-only --locked .
will not install packages that will be installed with opam-monorepo pull
(#237, @Leonidas-from-XIV)--ocaml-version
. (#269, @NathanReb)--repo
option to --root
to make it more straightforward that this is referring to the project root (#218, @samoht)--verbose
(#229, @emillon)opam-monorepo depext
, especially for non-interactive shells (#216, @samoht)--keep-git-dir
flag to the pull
command that can be used to keep the [.git] directory after pulling the vendored sources. (#160, @rizo)duniverse
(#206, @emillon)OPAMROOT
to accept non-default paths (#197, #198, @Leonidas-from-XIV)2.1~rc2
to 2.1
(#204, @NathanReb)zdev
if it is defined (#183, @emillon)-l
/--lockfile
command line option to explicitly set the lockfile to use or generate in pull
or lock
(#163, @NathanReb)pin-depends
field in opam files. When present, these will be used by the solver (#153, #159, #167, @rizo, @TheLortex, @NathanReb).lock
performance (about 2x faster) by loading the repository state only once (#188, #192, @emillon)pull
command would fail if it used CRLF for new lines. (#191, @NathanReb)pull
as it only use it to suggest updating the lang version for convenience (#191, @NathanReb)pull
and lock
would expect the lockfile to sit in a different place and pull would fail. pull
now simply looks for a .opam.locked
file and pulls it unless there are multiple matching files in the repository's root. (#163, @NathanReb)lock
now skips resolution when the ref is actually a commit pointed by a remote branch or when it looks like a commit (hexadecimal characters only, at least 7 characters-long). (#195, fixes #127, @TheLortex)--ocaml-version
argument to lock
: it allows to determine the ocaml version in the lockfile that's being generated (#161, @pitag-ha)jbuilder
from the lock step. Since dune 2.0, jbuild
files are not supported. A new --allow-jbuilder
option have been added to enable the old behavior.opam-file-format
latest versions as building with dune. (#176, @NathanReb)ocaml-option-*
packages. (#178, @NathanReb)git+https
(#166, @TheLortex)duniverse
(#158, @rizo)--recurse-opam
option for the monorepo lock phase: correctly perform special directory filtering, add an error message when two versions of the same package opam file exist in the source tree, perform package name filtering before checking for uniqueness (#151, @TheLortex)Initial release