This was initially meant to save space in docker containers,
but breaks several use cases and runner images shouldn't have
space constraints.
Also fixes: https://github.com/haskell/actions/issues/176
We use it during installation and add it to PATH, but then
don't instruct ghcup to actually use this directory at runtime.
This leads to:
1. ghcup is in /usr/local/.ghcup/bin/
2. `ghcup install cabal latest` will actually install into ~/.ghcup/bin/
3. since ~/.ghcup/bin/ is not in PATH, but /usr/local/.ghcup/bin/ is,
the new binary is not visible to the user
This issues does not exist on darwin, because there we use
~/.ghcup/bin/.
https://downloads.haskell.org/ghcup/tmp/aarch64-linux-ghcup-0.1.18.1
* Expose ghcup binary to PATH on windows
The bootstrap-haskell.ps1 script uses
'[System.EnvironmentVariableTarget]::User' instead of
'[System.EnvironmentVariableTarget]::Machine', so it appears
ghcup env vars and PATH update never make it. Do these manually
for now.
* Set CABAL_DIR and make sure config is adjusted
The config adjustment usually includes adding msys2 directories,
so cabal can find `pkg-config` and libraries, e.g.:
+ C: \ghcup\msys64\mingw64\bin
+ extra-include-dirs: C:\ghcup\msys64\mingw64\include
+ extra-lib-dirs: C:\ghcup\msys64\mingw64\lib
- extra-prog-path: C:\cabal\bin
+ extra-prog-path: C:\ghcup\bin,
* Expose cabal dir to PATH as well
* Use Set-SystemVariable
* Fix tests
* Use hardcoded cabal dir
* Fix bootstrap-haskell
* Move test after installation
* Print ghcup installation message
* Don't adjust cabal.config (to include mingw paths)
This may break setups.
Julian Ospald