On breaking compat for the CLI for 2.1 #4503
Description
Hi,
I recently migrated to the last version of opam-git, and noticed that opam now breaks compat with the CLI. In particular opam config var is not available anymore, and opam var must be used instead.
This is just a head's up that it break at the very least the following tools (and probably more):
- merlin
- ocp-browser
- tuareg
- dune
thanksfully this can be rolledback using the OPAMCLI variable, but I'm not sure the change is worth it.
# opam config report
# opam-version 2.1.0~beta4 (8ce5e420f8007fd8d7ad56fb6293af6f5469a432)
# self-upgrade no
# system arch=x86_64 os=linux os-distribution=arch os-version=rolling
# solver builtin-mccs+glpk
# install-criteria -removed,-count[hidden-version,changed],-count[version-lag,request],-count[version-lag,changed],-count[missing-depexts,changed],-changed
# upgrade-criteria -removed,-count[hidden-version,changed],-count[version-lag,solution],-count[missing-depexts,changed],-new
# jobs 3
# repositories 2 (http), 1 (local), 4 (version-controlled) (default repo at 1aa37053)
# pinned 4 (git)
# current-switch main
# read-state Not_found