Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Document the "opam package version-string resolution"? #4239

Open
erikmd opened this issue Jun 21, 2020 · 0 comments
Open

Document the "opam package version-string resolution"? #4239

erikmd opened this issue Jun 21, 2020 · 0 comments

Comments

@erikmd
Copy link

erikmd commented Jun 21, 2020

.opam file specifications directly-committed in source repositories do not usually contain a version,
and I believe the "opam package (version-string) resolution" (namely, the order in which the various places potentially-containing a package (and thereby specifying a version) are queried when installing a given package name) is not directly documented in the opam manual. Hence this issue :)

Actually beyond the code itself, I only found that other issue #2932 (comment) by @jeremiedimino that mentioned this:

  1. use the version specified on the command line, if any
  2. use the version: field in the opam file of the pinned package, if any
  3. use the latest version available in the package repository, if a package with the same name already exists
  4. ~unknown with opam1 and ~dev (+dev?) with opam2

(I also Cc @ejgallego, @Zimmi48, @CohenCyril, @affeldt-aist as we recently discussed of that feature in some GitHub issues
(the issues being coq/coq#11038, math-comp/analysis#218 just FTR))

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

2 participants