I’m wondering whether there are best practices regarding the
opam install --locked option, especially from a CI and packaging perspective?
The doc says it allows one “to share a set of dependencies that you know (locally) the project is working with”.
But to be more precise:
- is it advised to commit a
project.opam.lockedin all projects?
if yes, this yields two standard ways to build the project (with
opam install --locked or simply with
opam install), so:
should the CI configuration build the project using the
project.opamspec, or both (with two separated jobs in a fresh environment)?
and for end users (assuming they build the project in a fresh switch), should we recommend using the
As an aside, are there standard ways (maybe semi-automatic?) to facilitate the update of a
Thanks for any references/suggestions,