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
One behavioural change from OPAM 1.1 and 1.2 that surprised me is the auto-detection of the repo type.
If I have a local git checkout of opam-repository and do a opam remote add ~/opam-repository, it now becomes a git remote, and local changes are only reflected if I commit. The default used to be that this would be a local remote and rsynched (much more convenient for local use).
I can get the old behaviour back by adding -k local, but I just wanted to check that this was an intended change.
The text was updated successfully, but these errors were encountered:
Being consistent is good, and I'm not against the new behaviour. However, it's definitely worth noting in the release notes, as my old 1.1 workflow simply didn't work anymore without the -k local addition. More typing needed, but that's progress eh :-)
Yes, this is quite new, but otherwise confusing build artefacts could get in the way. Note that you can save one keystroke by using the now preferred -k path
Indeed this is not even in the changelog, and needs to be notified.
One behavioural change from OPAM 1.1 and 1.2 that surprised me is the auto-detection of the repo type.
If I have a local git checkout of
opam-repository
and do aopam remote add ~/opam-repository
, it now becomes agit
remote, and local changes are only reflected if I commit. The default used to be that this would be alocal
remote and rsynched (much more convenient for local use).I can get the old behaviour back by adding
-k local
, but I just wanted to check that this was an intended change.The text was updated successfully, but these errors were encountered: