-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
opam pin remove
behaviour
#3630
Comments
It's only if version |
I don't understand your answer. |
If that's not clear what I'm asking is that when you remove a dev pin it tries to install the latest version of the package not the version that was there when you pinned. |
It's clear :) What I wanted to say (with few words) is that there is two processes:
It's a design choice, that can be discussed ofc. |
IIRC there's actually a workaround -- the problem is that I usually forget about it and blindly issue an I was always a bit uncomfortable with it because you basically you go through an inconsistent switch state. But if people consider that's good enough maybe it's not worth changing/complexifying things and this can be closed. (I let you do if you think so) |
After discussion with @AltGr, it makes sense to remove that specific behaviour, in order to always have the last repo version of the newly unpinned package. |
Thanks! |
Excellent ! |
I think this used to work in the v2 betas but it seems it no longer.
When you release you usually have the package you release as a
pin
on the current versionX
. You submit to the opam repo versionX+1
. Then when youopam update
and have the updateX+1
from the OCaml opam repository, you want to remove the pin and recompile withX+1
. The current behaviour when youopam pin remove
is to recompile withX
which is annoying if your package has many deps, since you have to follow with a recompile withX+1
.The text was updated successfully, but these errors were encountered: