RFC: include a cabal-install executable in future GHC releases

[Carter Schonwald]

the point is: there should be some *easy* way to get/install cabal-install
binaries for those who aren't in a situation where haskell platform is
appropriate.

I generally regard haskell platform as "for students", "people with
enterprise support cycles" and "oh shit, my haskelll install is borked and
i need to get things working again right nowwwwww". I understand that
certain distros/package managers regard it as a stable substrate
(rightfully, cf my remark about support cycles).

But that doesn't preclude people from doing their own setup, and if that is
common place (as I believe it is, though i've not done a survey), having
binaries at are easy to install is a reasonable goal!

-Carter


On Sat, Jan 25, 2014 at 12:59 PM, Ganesh Sittampalam <ganesh at earth.li>wrote:

> > I think that "something" need to be done to make it easier to set up >
> GHC + cabal, independently of HP (unless HP becomes the "one true
> > way" to install Haskell, which I doubt is the case).
>
> Isn't that what this banner on
> http://www.haskell.org/ghc/download_ghc_7_6_3 is supposed to signify?
>
> "Stop!
>
> For most users, we recommend installing the Haskell Platform instead of
> GHC. The current Haskell Platform release includes a recent GHC release
> as well as some other tools (such as cabal), and a larger set of
> libraries that are known to work together."
>
> For the people who want GHC to include cabal-install, what are the
> obstacles to using the Haskell Platform instead?
>
> One possibility I can see is disk space. The other reason, raised by
> Carter at the start of this thread, is wanting to use the freshest GHC.
>
> Cheers,
>
> Ganesh
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://www.haskell.org/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20140125/83bc6253/attachment.html>