As part of crystal-lang/crystal#6170, it makes sense to test Shards on MSYS2 and package Shards for it as well. The bad news is that all the resolvers are problematic on MSYS2:
- Mercurial is only available from the MSYS environment, and installs
/usr/bin/hg, a Python script with a shebang, which Process.run doesn't handle. Nor is running the script with Python expected on Windows, since Mercurial packages hg.exe using PyOxidizer; the specs will pass if this executable is exposed inside MSYS2 with something like PATH="$(cygpath $PROGRAMFILES)/Mercurial:$PATH".
- Fossil has a UCRT64 build but it is completely broken. It is a single executable, so downloading the official Windows build somewhere to
$PATH would work. (If obtained via WinGet, it should be available at $(cygpath $LOCALAPPDATA)/Microsoft/WinGet/Links.)
- No specs are affected by MSYS Git, but it has its own issues.
Everything else seems to work fine.
As part of crystal-lang/crystal#6170, it makes sense to test Shards on MSYS2 and package Shards for it as well. The bad news is that all the resolvers are problematic on MSYS2:
/usr/bin/hg, a Python script with a shebang, whichProcess.rundoesn't handle. Nor is running the script with Python expected on Windows, since Mercurial packageshg.exeusing PyOxidizer; the specs will pass if this executable is exposed inside MSYS2 with something likePATH="$(cygpath $PROGRAMFILES)/Mercurial:$PATH".$PATHwould work. (If obtained via WinGet, it should be available at$(cygpath $LOCALAPPDATA)/Microsoft/WinGet/Links.)Everything else seems to work fine.