We are pleased to announce the release of opam 2.0.7 and an 2.1.0 alpha . This 2.0.7 version contains backported fixes, you can find more information in this blog post . The 2.1.0~alpha contains many new features (cf. blog post or release note ). If you want to take a look, a few glitches or regressi…

I had looked on the issue tracker on Github and found some somewhat fizzled out discussions on cross compilation support. Is there somewhere this might be discussed further? I didn’t see any mention of it in these release notes.

When using the new opam lock functionality, once we create a foo.opam.lock file, how do we use when we want to replicate the same opam environment in another pc? Does the opam install . command check if there exists a foo.opam.lock file and use it or is it perhaps the opam switch create . checks f…

Additionally, is there a way to define a development only package dependency in .opam file depends section, much like npm dev-dependencies section? For example I want to add merlin, ocamlformat to the depends package list, however I don’t want the package to be built/installed/reinstalled when thes…

You can use opam install . --locked to tell opam to use the lock file. I’m not sure about the dev dependencies part.

Ah, it seems it is an opt-in. Yep --locked works. @AltGr wouldn’t it be better perhaps if this option is the default on opam install . and opam switch create . commands ?

I actually agree with the current opam install behaviour of not using the lockfile. Npm and Esy actually behave the same way–only install exact locked versions if you explicitly say so. This is done in CI/CD builds for reproducibility but for local development you would usually want to install whate…

[image] yawaramin: Npm and Esy actually behave the same way–only install exact locked versions if you explicitly say so. I believe this is incorrect, npm (and yarn) and esy use lockfile if it exists when running install command. You can force finding new solution with esy solve --force

Ah, my mistake about Esy, thanks Andrey. Regarding npm, I believe it has the ci command for doing explicitly locked installs. So I assumed that the regular npm install command does update lockfiles i.e. dependencies. Maybe wrong assumption!

For yarn at least – according to this doc https://classic.yarnpkg.com/en/docs/cli/install/ , yarn’s first preference is to use yarn.lock file if present.

@rjbou @AltGr and @dra27 Thank you for all the work on opam! I’m currently encountering an opam-installer compilation issue on the master branch at 3def1a6d1ff102aaa60 . I’ve pasted the details on https://github.com/ocaml/opam/issues/4173

[ANN] opam 2.0.7 and 2.1.0 alpha

Ecosystem

andreypopp May 1, 2020, 8:17am 10

I believe this is incorrect, npm (and yarn) and esy use lockfile if it exists when running install command. You can force finding new solution with

esy solve --force

Topic		Replies	Views
[ANN] opam 2.1.0! Ecosystem opam , announce	6	2575	August 5, 2021
[ANN] opam 2.1.0~beta4 Ecosystem opam , announce	0	2169	February 10, 2021
[ANN] opam 2.2.0~alpha release! Ecosystem opam , announce	1	1584	July 4, 2023
Opam lock file mechanism? Learning	6	1421	July 18, 2018
Should opam use a lockfile by default? Community opam	23	3693	October 15, 2019

[ANN] opam 2.0.7 and 2.1.0 alpha

Related topics