And 3 respective snapshots: lts-12.26, lts-13.12, nightly-2018-12-15.
I think that at least one of the 2 "extra" snapshots/ghcs can be eliminated.
As a side note, stack script does not use .stack/config.yaml so it reinstalls ghc-8.6.2 in the default local-programs-path if you have change it to other location in the config.
Hopefully it seems it is going to honour it: https://github.com/commercialhaskell/stack/issues/3887#issuecomment-478650724
@jneira apparently the stack bug is already closed. Can you recheck with stack-git?
Of course, i've just downloaded the artifacts of build here: https://dev.azure.com/commercialhaskell/stack/_build/results?buildId=1170
and it honours my user config file. 馃憤
Yes, normally only one additional snapshot should be required.
The PR #1168 may address this problem.
This is fixed in #1168
It isn't merged as of April 20
Should be fixed now, please check!
On a related note, is it possible to use
system-ghc: true in shake.yaml to avoid stack having to download another snapshot/compiler? Assuming that install.hs is backwards compatible with other versions of ghc?
Possibly yes. @power-fungus?
I will test that. What happens if there is no system-ghc?
Afaik, it errros out.
Should be fixed now, please check!
works for me
Can the shake resolver be bumped to nightly-2019-04-30 so that it's in sync with stack.yaml?
Have the issues with 8.6.3 on windows been fixed for 8.6.5?
The issue of 8.6.3 ist fixed on 8.6.4 already. At least, I can build hie 8.6.4 on windows.
Regarding bumping shake-resolver, in general, there is no problem with that, in general. We can open a new issue for that.
I opened an issue for bumping the shake resolver #1266.