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
$ git clone <my-ocaml-project> -b main
$ cd my-ocaml-project
$ opam switch create .
[creates a local switch and pin the project packages in it]
$ opam switch -c test
$ git branch -D main
$ opam update --dev
<><> Synchronising development packages <><><><><><><><><><><><><><><><><><> 🐫
[ERROR] Could not synchronize [....]
[mypkg] fetching sources failed: [...]
The git branch -D is only here to highlight the problem.
The issue is that the info from the opam files can be out-of-date or plain wrong.
In my opinion there should be an automated by of detecting that the pinned packages from the local directory in a local switch should be changed. opam update or opam install might be good places to check that and automatically change it.
There might need to be a new flag on pinned packages to tell it has been automatically added by opam and not manually by the user to avoid overwritting the user’s will.
The text was updated successfully, but these errors were encountered:
opam switch create . should pin to HEAD rather than current branch
For consistency, on later opam install . or opam pin, we should detect new pins to the switch-root directory (or a child ?) and direct them to HEAD rather than current branch
opam update could print a warning when the opam files present changed ?
The
git branch -D
is only here to highlight the problem.The issue is that the info from the opam files can be out-of-date or plain wrong.
In my opinion there should be an automated by of detecting that the pinned packages from the local directory in a local switch should be changed.
opam update
oropam install
might be good places to check that and automatically change it.There might need to be a new flag on pinned packages to tell it has been automatically added by opam and not manually by the user to avoid overwritting the user’s will.
The text was updated successfully, but these errors were encountered: