Is setting OPAM_CLI from the action necessary?

[jchavarri]

Currently, it is possible to use opam 2.2 through the recently added allow-prelease-opam config (thanks!).

However, when one tries to use features from this version, like the --with-dev-setup flag, opam will error with:

opam: --with-dev-setup was added in version 2.2 of the opam CLI, but version 2.0 has been requested, which is older.

The reason for this is that setup-ocaml will set OPAMCLI to 2.0 here:

setup-ocaml/packages/setup-ocaml/src/installer.ts

Line 38 in 06476c1

core.exportVariable("OPAMCLI", "2.0");

I wonder if setting this config in the action is strictly necessary? Wouldn't it be easier to just leave this version "float" and have opam used the latest version available?

[smorimoto]

See #711 🙂

[jchavarri]

Nice! For the record, I managed to work around the original issue by passing --cli flag to the opam command. Just mentioning in case the changes in #711 were somehow controversial, for some reason (maybe it's better to stick with a default version in all cases, idk).

[smorimoto]

It's true that you can use --cli to avoid the issue, but in cases where you want to allow pre-release, the environment variable is just noisy, so it seems sensible to leave it unset.

[smorimoto]

Shipped: https://github.com/ocaml/setup-ocaml/releases/tag/v2.1.1