You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.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:
use the version specified on the command line, if any
use the version: field in the opam file of the pinned package, if any
use the latest version available in the package repository, if a package with the same name already exists
.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:
(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))
The text was updated successfully, but these errors were encountered: