David Allsopp

> * now opam init works, but detects the ocamlc 4.14.0 from dkml 2.0.2 and uses it as a system switch Just to confirm or check further - this is...

@jonahbeckford - the only possibility for 2.2.0 is that `opam init` might recognise that there's an existing DKML installation and display a warning, rather than anything further. Although I agree...

Thanks for this - I expect it’ll take me a while to actually action it all, but I hope we can put this in place for the 2.4 release next...

We should add `--disable-dependency-generation` to the configure options (there's already `--disable-stdlib-manpages` there. Do the machines which are getting OOM fail with `-j16`? Testing on one of the high-core machines here...

This isn't Windows-specific: ``` opam@eb69dfc8d71b:~$ opam-dev install core_bench.v0.15.0 "ppx_expect>=v0.16.0" [ERROR] Package conflict! * No agreement on the version of ppx%5fexpect: - ppx_expect >= v0.16.0 - core_bench = v0.15.0 -> ppx_jane...

This is also present in 2.1 (but not 2.0) - looks like it would have come in with #4349 (although it's not necessarily an issue directly with the PR)

You're doing this with normal opam-repository, right? This simply doesn't work at the moment - opam-repository doesn't support building ocaml-base-compiler on MSVC.

Start in ocaml/opam#246 and go from there 🙂

(also https://fdopen.github.io/opam-repository-mingw/ if you're not already aware)

I'm on in this as part of the upgrade of `ocaml-base-compiler` packages to support Windows for 2.2.0