test all the methods on all the operating systems #247
Conversation
it is available when computing the cache key but not when computing the build name?
...then why is cabal making a symlink instead of a copy? |
|
According to the documentation, cabal should already use copy instead of symlink on Windows. This has been merged in February 2020. We're now in January 2021. Surely that code has been released since? |
|
Nope; even though cabal 3.2.0.0 (which github actions is using) was released in April 2020, it doesn't look like that patch made it in. So I'll just have to manually specify |
technically I only need to do this on Windows, but there's no harm in doing it on all the platforms.
|
Okay, now that I've finally figured out the right PowerShell syntax, I see that the installation-method detection code doesn't work on Windows. Hawk used to work on Windows, but it's clear that it's now broken. I don't think it would be too hard to make Hawk work on Windows, but with #239 and now this, it's starting to become a sizeable chunk of work. Since there are so many other things to fix in this codebase, I think it would be better to cut my losses now: I am dropping support for Windows (until I get feedback from users saying they want it). See #248. |
currently, hawk builds and installs fine on Windows, and then disappointingly fails at runtime. better tell the user in advance that it isn't going to work.
This reverts commit 84d7896.
I was previously using "stack build" in both the "oldest" and "stable" configurations. I now want "stack install" so I can confirm that running the stack executable from the command-line works, but I forgot to change one of the two "stack build"s to "stack install".
Fixes #245. Hopefully. But realistically not; these things always take several attempts.