Clarification: behavior of interaction between opam pin --kind version
and opam pin --kind path
#3983
Labels
opam pin --kind version
and opam pin --kind path
#3983
(This is a question about a somewhat unintuitive behavior related to
opam pin
; sorry if it is already mentioned somewhere.)One user of our opam package used a
opam pin --kind path <file.tar.gz>
to install a custom release whose version number is identical to the "official" release (frama-c 19.0). They proceeded as follows:The package was path-pinned to version 19.0. Then they noticed an issue and wanted to install the "official" package from opam, so they did as they were used to:
He expected the new version to be that of the official opam repository, but opam in fact recompiled the same path-pinned package. I could reproduce it with opam 2.0.4.
My question is: is this intended behavior? I'm asking in case it might not be. I agree that having a custom
.tar.gz
with the same version number is not ideal, and possibly part of the issue, but still, I'd have expected that, when re-pinning a package, opam would not consider the soon-to-be-unpinned packages among the possible candidates.The text was updated successfully, but these errors were encountered: