Hand over GHC management to ghcup from stack

The new user using stack with default settings will typically end up with a duplicated development environment, as stack will try to pull GHC versions whenever it cannot find a version required by a project that is already installed from GHCup.

This notice helps avoiding the issue. One might argue that this does not belong to ghcup's documentation, but this very docs already hints at such a notice (https://www.haskell.org/ghcup/about/#why-should-i-use-ghcup-over-stack).

changed title from Stack using ghcup ghc to Hand over GHC management to ghcup from stack

The problem with system-ghc: true is that it picks whatever ghc is in PATH (it doesn't try ghc-x.x.x).

In the vscode extension, that's not a problem. For the normal cli workflow, it is.

That's why I created: https://github.com/commercialhaskell/stack/pull/5585

But stack developers haven't responded to it.

added 1 commit

• ce65990f - Removed leftover from separate PR.

Compare with previous version

added 1 commit

• 571104e6 - Removed leftover from separate PR.

Compare with previous version

First of all sorry: I let a leftover from my other pending PR spill over this one. Should be fixed now (only 1 file changed).

Okay, so with or without system-ghc: true there is a problem. But isn't the problem caused by using it likely to be solved by the stack devs anyway; whereas the problem caused by not using it can be solved right here right now (i.e. avoid duplicating GHCs)?

But isn't the problem caused by using it likely to be solved by the stack devs anyway

Don't think so

whereas the problem caused by not using it can be solved right here right now (i.e. avoid duplicating GHCs)

But this requires further instructions. Otherwise the user will have to debug why their project with a different LTS doesn't build.

added stale label