-
Notifications
You must be signed in to change notification settings - Fork 54
Conversation
CI suggests that with this PR, on Windows the requested version of |
It is OK for you to use this code, it seems to be working to test GHC prereleases on windows for Haskell Language Server, which is all I really intended. We may go back to using the master branch of I'm really not the best person to be maintaining this, I just tried to do the minimal amount of changes to achieve the aforementioned goal. It took me quite a while to figure out how to compile the typescript to javascript. |
Right, I can reproduce this. I will attempt to fix. |
I rely on |
I'm somewhat biased here towards not removing chocolatey and instead leaving it as a fallback. As long as chocolatey and the ppa remain fallbacks, their codepaths will only be triggered if ghcup doesn't work, and then we can guarantee some sort of backwards compatibility. One reason I'm interested in the backwards compatibility is that this action does work on self hosted runners and I'm sure there are likely people out there who are running it with chocolatey installed and not much else. It also gives people the opportunity to pin to some of chocolatey's special ghc versions (like ghc 8.10.2.2) which fixed a few windows+chocolatey specific stuff. If we're using ghcup from the path, we should do so for everything else as well, but we'll also need to fall back to installing the newest version of ghcup and trying that again, in case someone has a version of ghcup that's too old for the version of ghc or cabal that they're trying to install. So the fallback in that case would be:
|
@FinleyMcIlwaine and I have got this working now, please feel free to take over to restore chocolatey as fallback. |
It's hard to follow the discussion about GHC on Windows in GitHub virtual environments scattered over this bug tracker, but I'll offer my 2c here... There is absolutely enough to have one way to set up GHC (on Windows or otherwise). If someone wants a particular method, they should set it up themselves. Otherwise, the 95% who are not interested in other methods will have to pay with the CI time. |
Rebasing this on latest CI. |
@Mergifyio rebase |
❌ Pull request can't be updated with latest base branch changesMergify needs the author permission to update the base branch of the pull request. |
@wz1000 : Could you please give authorization to rebase this PR, or maybe rebase it manually? I'd like to test it with latest CI. |
Atm, this PR also seems to destroy the Ubuntu-20.04 will only support a few legacy GHCs: relevant are 7.4.2 7.2.2 7.0.4 (and maybe 7.10.3). https://launchpad.net/~hvr/+archive/ubuntu/ghc?field.series_filter=focal |
I can't authorize changes to this PR because I am not the one who opened it. |
Ah sorry, I thought this was something with your local repo (PR source). Then maybe let's continue on: @wz1000 You already have write access to this repo. |
ghcup
on windows@wz1000 : I picked this PR up from your fork proactively, because Windows setup is currently broken, and it would be good to have a solution.
Would you be willing to contribute here?
Is this code from your fork something we may and should merge?
Refs:
ghcup
not found onwindows-2022
version 20230214.1 #191