Mike Pilgrem

On "_Do users stick around with old versions of GHC and for how many years?_", you may be interested in this, which is the discussion on Stack's repository (with links...

For what it is worth, my solution to the problem of achieving consistency with Stack's documentation was (1) to create a glossary (https://docs.haskellstack.org/en/stable/glossary/) and then (2) to apply it consistently...

A difference between the two builds above is that, in the linking step, Cabal calls GHC 9.6.5 with additional arguments not present in the GHC 9.6.4 example: ~~~text "-dynload deploy"...

Looking at: https://downloads.haskell.org/~ghc/9.6.5/docs/users_guide/shared_libs.html#finding-shared-libraries-at-runtime, I get the impression that `-dynload deploy` may be a GHC option that is not applicable on Windows.

I don't think so - looks to me like a regression introduced into Cabal, not GHC. EDIT: unless you mean something to warn the GHC developers that there is this...

@psibi, thanks. I've raised https://github.com/commercialhaskell/http-download/pull/5 so the `http-download` package can rely on `crypton-conduit`. I am happy to share the burden of looking after `crypton-conduit`, if you want to add me...

I think the CI is failing for reasons unconnected with this pull request.

I've rebased on `master`.

I've tidied-up manually.

I'll try to give the fix some attention in the coming days.