opam 2.0.4 release
We are pleased to announce the release of opam 2.0.4.
This new version contains some backported fixes:
- Sandboxing on macOS: considering the possibility that TMPDIR is unset [#3597 @herbelin - fix #3576]
- display: Fix
opam config var
display, aligned onopam config list
[#3723 @rjbou - rel. #3717] - pin:
- opam clean: Ignore errors trying to remove directories [#3732 @kit-ty-kate]
- remove wrong "mismatched extra-files" warning [#3744 @rjbou]
- urls: fix hg opam 1.2 url parsing [#3754 @rjbou]
- lint: update message of warning 47, to avoid confusion because of missing
synopsis
field internally inferred fromdescr
[#3753 @rjbou - fix #3738] - system:
- lock & signals: don't interrupt at non terminal signals [#3541 @rjbou]
- shell: fix fish manpath setting [#3728 @gregory-nisbet]
- git: use
diff.noprefix=false
config argument to overwrite user defined configuration [#3788 @rjbou, #3628 @Blaisorblade - fix #3627]
- dirtrack: fix precise tracking mode [#3796 @rjbou]
- fix some mispellings [#3731 @MisterDA]
- CI enhancement & fixes [#3706 @dra27, #3748 @rjbou, #3801 @rjbou]
Note: To homogenise macOS name on system detection, we decided to keep
macos
, and convertdarwin
tomacos
in opam. For the moment, to not break jobs & CIs, we keep uploadingdarwin
&macos
binaries, but from the 2.1.0 release, onlymacos
ones will be kept.
Installation instructions (unchanged):
-
From binaries: run
sh <(curl -sL https://opam.ocaml.org/install.sh)
or download manually from the Github "Releases" page to your PATH. In this case, don't forget to run
opam init --reinit -ni
to enable sandboxing if you had version 2.0.0~rc manually installed or to update you sandbox script. -
From source, using opam:
opam update; opam install opam-devel
(then copy the opam binary to your PATH as explained, and don't forget to run
opam init --reinit -ni
to enable sandboxing if you had version 2.0.0~rc manually installed or to update you sandbox script) -
From source, manually: see the instructions in the README.
We hope you enjoy this new minor version, and remain open to bug reports and suggestions.
NOTE: this article is cross-posted on opam.ocaml.org and ocamlpro.com. Please head to the latter for the comments!