*tl;dr: We'd like to incorporate stack into Haskell Platform, and stop
shipping pre-built packages, so we banish cabal hell, and have a single
common way to 'get Haskell' that just works.*
At ICFP '14, there were several long group discussions of the state of
"getting Haskell", including Haskell P
I’m ccing cabal-devel, as that list seems pertinent to this discussion too. In
general I’m in favor of unifying efforts such as this.
For windows, I’d still like the _option_ to get prebuilt library binaries for
the full platform db. The modularity means that they can be just downloaded in
a se
No - we are not talking about the upcoming, 7.10.2 HP release. It would for
the next major release after that.
Yes, stack has only been out ~1 month, but it has already shown traction in
the community, and it has a clear working solution for managing "curated"
pacakge sets, like Haskell Platform.
I think it depends somewhat on operating system, since there are
permissions issues to be dealt with regarding user vs global installation.
In principle though: I think the HP installers would install to a
non-stack-specific location, and then stack would simply use that GHC based
on its inclusion
2015-07-12 18:03 GMT+02:00 Mark Lentczner :
>
>- [...] Haskell Platform becomes the standard way to get *GHC* and
>related tools: *alex*, *cabal*, *happy*, *hscolour*, and *stack*. [...]
>
> What about haddock? I guess "GHC" implicitly means "haddock", too.
Apart from that +1, modulo some
