stack VS Cabal

Probably this issue: https://github.com/commercialhaskell/stack/issues/5607

Here is link number 1 - Previous text "PRs"

If you want better integration with ghcup, start reviewing my PRs.

and need to change my stack to use a newer version of ghc that nixpkgs switched to like ghc8106. This is actually open as an issue in the stack project https://github.com/commercialhaskell/stack/issues/4539. However it's more than just a stack issue, even if stack were to fix this part of the problem is haskell-language-server that runs haskell-lsp keeps updating its supported ghc versions. Fixing stack but being unable to use my development environment doesn't do me much good.

Following the hint to https://github.com/commercialhaskell/stack/issues/4510, I found https://github.com/commercialhaskell/stack/issues/4897 and "Overriding GHC boot packages results in any other GHC boot packages depending on it being no longer available as a dependency".

There was a proposal to introduce a brokering tool to handle this communication, but the maintainer of ghcup didn't like it very much, because this adds yet another program into the mix. They would prefer it if stack would add a hooking mechanism such that users (or ghcup automatically) can change the mechanism that stack uses for installing GHC.

The 1.9.3 release is on github here: https://github.com/commercialhaskell/stack/releases/tag/v1.9.3

It seems like you just might be able to follow the steps in: https://github.com/commercialhaskell/stack/issues/3987#issuecomment-385127302

Then I saw these: https://github.com/haskell/cabal/issues/1802

Cabal's Version type might be interesting to you.

There's a long discussion on this issue. I think a fundamental problem is highlighted here. Just below that is a solution in the form of a preprocessor for cabal files.

Hopefully my most anticipated fix makes it in to the next version: source-repository-package can't handle git branches. It's supposedly a simple change, but a PR's been up for over a year and seems to be stuck in limbo. Meanwhile, I've had to add stupid workarounds for the issue twice this morning. I'd love to help but I'm totally useless with Git...

Yeah, it would be so nice to get it fixed. A close second for me is the missing support for submodules in source-repository-package, also with a limbo PR.

Will be fixed in 3.6: https://github.com/haskell/cabal/pull/7354

I found this issue on the cabal github which seems to be related: https://github.com/haskell/cabal/issues/2997

For a full set of release notes, see https://github.com/haskell/cabal/blob/master/release-notes/Cabal-3.6.0.0.md. If you have issues, we'd love to hear about there here: https://github.com/haskell/cabal/issues.

Here are some more details, although not too many if you aren't already familiar with it: https://github.com/haskell/cabal/issues/7489