Drom doesn't work on windows with opam 2.2

[Ninjapouet]

AFAIU, with opam 2.2 comes new installation procedure that installs opam in a Windows path (within %APPDATA%). However, drom looks for opam in a traditionnal way in $(HOME)/.opam directory. As it doesn't find opam, it systematically tries to opam init at each call... Looking for hardcoded directories is too fragile and should be avoided.

This is related to #227

[Ninjapouet]

Setting explicitly OPAMROOT is a possible workaround.

[zapashcanon]

Using directories (which IIRC is already a dependency of drom) should allow to properly locate the place where opam is thanks to SHGetKnownFolderPath.

[Ninjapouet]

Thanks for explaining that drom should work but it does not. Like I said, using opam 2.2 installed on Windows and with MSYS2 backend leads to drom compiled in MSYS2 continue searching for Linux paths and not Windows' (although Sys.os_type gives "Win32" on MSYS2).