<div dir="ltr">Ok,<div><br></div><div style>so either</div><div style><br></div><div style>a) provide a ghc + cabal-install binary included (heck, its easy to update to a cabal install anyways, and the ~/.cabal/bin path will be before wherever the ghc pkgs are installed anyways. The same argument could be made for packaging happy and alex with ghc too! ). After all, i already have a happy / alex from cabal-installing them from earlier, why should ghc install it again? :p </div>
<div style><br></div><div style><br></div><div style><br></div><div style>b) either way, perhaps the cabal-install devs/maintainers should standardize making some binaries available</div><div style><br></div><div style><br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jan 21, 2014 at 3:44 PM, Ganesh Sittampalam <span dir="ltr"><<a href="mailto:ganesh@earth.li" target="_blank">ganesh@earth.li</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If you can't find any better options, I can try to run a buildbot on a<br>
laptop that's probably mostly online.<br>
<div class="im"><br>
<br>
On 21/01/2014 19:32, Johan Tibell wrote:<br>
> We could offer OS X and Linux binaries in addition to the Windows<br>
> binaries already downloaded on the cabal home page<br>
> (<a href="http://www.haskell.org/cabal/" target="_blank">http://www.haskell.org/cabal/</a>) if someone could commit to building them.<br>
><br>
> Aside: Right now building the Windows binaries is a very ad-hoc process<br>
> (I email Mikhail who has a Windows machine and ask him to build one).<br>
> I'm not very keen to make the process even slower, given that that will<br>
> mean I will make fewer cabal releases. Ideally the binaries could be<br>
> produced on a build bot. The very least we should have the Makefile in<br>
> the cabal repo being able to create the binary in a reproducible manner.<br>
><br>
> -- Johan<br>
><br>
><br>
><br>
> On Tue, Jan 21, 2014 at 11:22 AM, Ganesh Sittampalam <<a href="mailto:ganesh@earth.li">ganesh@earth.li</a><br>
</div><div><div class="h5">> <mailto:<a href="mailto:ganesh@earth.li">ganesh@earth.li</a>>> wrote:<br>
><br>
> I feel this blurs the roles of GHC and the Platform.<br>
><br>
> Can't the cabal-install that comes with the Platform can be used with a<br>
> later GHC installation? If that's correct, then the only use case that<br>
> this proposal covers is someone who wants to use a bleeding edge GHC and<br>
> no other version on a new machine. A separate binary distribution of<br>
> cabal-install should be more than adequate for that and it avoids<br>
> coupling GHC to other things.<br>
><br>
> So a weak -1.<br>
><br>
><br>
> On 20/01/2014 00:02, Carter Schonwald wrote:<br>
> > Hey everyone,<br>
> ><br>
> > I'd like to propose that GHC releases 7.8.1 onwards include a<br>
> > cabal-install (aka cabal) executable, but not include the library deps<br>
> > of cabal-install that aren't already distributed with ghc.(unless ghc<br>
> > should have those deps baked in, which theres very very good<br>
> reasons not<br>
> > to do.).<br>
> ><br>
> > currently if someone wants just a basic haskell install of the<br>
> freshest<br>
> > ghc they have to install a ghc bindist, then do a boostrap build of<br>
> > cabal-install by hand (if they want to actually get anything done<br>
> :) ).<br>
> ><br>
> > This is not a human friendly situation for folks who are new to<br>
> haskell<br>
> > tooling, but want to try out haskell dev on a server style vm or<br>
> the like!<br>
> ><br>
> > point being: It'd be great for haskell usability (and egads amounts of<br>
> > config time, even by seasoned users) the ghc bindists / installers<br>
> > included a cabal-install binary<br>
> ><br>
> > thoughts?<br>
> > -Carter<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Libraries mailing list<br>
</div></div>> > <a href="mailto:Libraries@haskell.org">Libraries@haskell.org</a> <mailto:<a href="mailto:Libraries@haskell.org">Libraries@haskell.org</a>><br>
<div class="im">> > <a href="http://www.haskell.org/mailman/listinfo/libraries" target="_blank">http://www.haskell.org/mailman/listinfo/libraries</a><br>
> ><br>
><br>
> _______________________________________________<br>
> Libraries mailing list<br>
</div>> <a href="mailto:Libraries@haskell.org">Libraries@haskell.org</a> <mailto:<a href="mailto:Libraries@haskell.org">Libraries@haskell.org</a>><br>
> <a href="http://www.haskell.org/mailman/listinfo/libraries" target="_blank">http://www.haskell.org/mailman/listinfo/libraries</a><br>
><br>
><br>
<br>
</blockquote></div><br></div>