stack VS Cabal

In YAML configuration files, the hackage-security key of the package-index key or the package-indices item can be omitted, and the Hackage Security configuration for the item will default to that for the official Hackage server. See #5870.

See https://haskellstack.org/ for installation and upgrade instructions.

Yes, that is correct. Stack's allow-newer: true configuration has always actually meant 'ignore bounds'. However, the author of the allow-newer-deps development has in mind a further development that will introduce an actual ignore-bounds key with the same expressive syntax that is used by Cabal. This is discussed at Stack #5910.

You can download binaries for this pre-release from: Release rc/v2.9.2.1 (release candidate) · commercialhaskell/stack · GitHub.

I'm trying to use the cabal mixins feature to automatically replace every implicit prelude import with a custom prelude (in this case relude). apparently it doesn't play well with `stack repl` https://github.com/commercialhaskell/stack/issues/5077 but I don't really use it anyway.

See https://haskellstack.org/ for installation and upgrade instructions.

stack build --coverage will generate a unified coverage report, even if there is only one *.tix file, in case a package has tested the library of another package that has not tested its own library. See #5713

You can download binaries for this pre-release from: https://github.com/commercialhaskell/stack/releases/tag/rc/v2.9.0.1.

The background to the reason why the default log level for Stack's script interpreter is 'error' can be found here: https://github.com/commercialhaskell/stack/issues/1472. Originally it was 'silent', but it was later increased to 'error'.

Funny that you say this, because stack used to clone the entire repository for each subdir, causing massive clone times that made it impossible to use for cardano projects: https://github.com/commercialhaskell/stack/issues/5411

At the moment, cabal-install doesn't support hpack natively but if the project can be build with cabal-install, you can run hpack manually to produce the .cabal file and utilise dr-cabal after that :)

Hm thanks for that, could try out some of those ideas. Here's the github issue i opened for this: https://github.com/haskell/cabal/issues/8580

Would really love it if the Cabal documentation had this as its own, highly visible entry. I submitted a pull request to that end.

Sometimes cabal's output is confusing with regards to optimization levels: https://github.com/haskell/cabal/issues/6221

Direct link to changelog: https://github.com/haskell/cabal/blob/master/release-notes/cabal-install-3.8.1.0.md

For example, this linked issue describes what appears to be a change, but is how I thought cabal already worked, so now I'm confused.

Unmarked "visibility: public" and "build-depends: pkg:lib" syntaxes as experimental, allowing Hackage upload of packages exposing or using multiple public libraries #6801 #7286 #8089

Ticket tracking support for this in cabal (so cabal repl will work for multiple components): https://github.com/haskell/cabal/issues/8238

ref. https://github.com/haskell/cabal/issues/7548

Found https://github.com/haskell/cabal/issues/8238. So the answer is seemingly "not yet".