-
Notifications
You must be signed in to change notification settings - Fork 19
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
Switching images to opam 2.1 by default #132
Comments
Are there any updates on this? Since mirage 4 requires opam-version >= 2.1.0 this would be very convenient :-) |
Ah, I see in #131 that |
FWIW |
yes, most of our CI projects start with:
|
There is also a dev version of opam available if you do this:
|
A year later, could opam 2.2 be used by default? Or is the "do some |
Doing |
set-opam-version.sh 2.1
added to images. It's justsudo ln -f /usr/bin/opam-$1 /usr/bin/opam && rm -rf ~/.opam && opam init -k local -a /home/opam/opam-repository --bare
(with error handling!)opam-depext
needs 2.1 support so that withOPAMCLI=2.0 opam depext package
worksENV OPAMCLI=2.0
and/usr/bin/opam
is/usr/bin/opam-2.1
by default. The root is therefore opam 2.1This presently blocked on the
opam depext
part, since there's no compatibility for previous versions. Switching to opam 2.1 will expose some uses to problems with opam's integrated depext on certain platforms.I propose
set-opam-version.sh
does a re-init for consistency: it only does fractionally more thanopam update
would, but it's a more consistent thing to do when downgrading from 2.1 to 2.0.The text was updated successfully, but these errors were encountered: