cmdliner 2.0.0 support

[dbuenzli]

It seems that the latest version of your package on the opam repository will not compile with the upcoming cmdliner 2.0.0 release.

This is either because you are using deprecated identifiers that are removed in 2.0.0 or because you still use argument converters as pairs which has been (sadly only silently) deprecated since 2017.

There are a few instruction here on how to make it compatible. If you run into problem or need more help use this issue, I'm listening.

[dbuenzli]

This concerns the packages opam-client.2.3.0 and opam-installer.2.3.0.

[kit-ty-kate]

Whether or not we can support cmdliner 2.0.0 will depend on the status of dbuenzli/cmdliner#200
If this is given the go ahead with no escape hatch, we'll probably sadly have no choice but fork the latest stable version of cmdliner 1.x instead.

[dbuenzli]

I don't think so, as mentioned in the instruction I linked to:

Projects can handle all breaking changes performed by 2.0 and still compile with cmdliner.1.3.0

[kit-ty-kate]

I'm not sure to understand. Do you mean cmdliner will still behave the same with regards to prefixes in 2.0.0?

[dbuenzli]

No it won't. But as far as I know these packages do not install opam the tool which is your worry.