I have a pull request here for review:
https://github.com/haskell/cabal/pull/2312
On 1 January 2015 at 18:43, Johan Tibell wrote:
> See https://github.com/haskell/cabal/issues/2310 for a continuation of
> the sad bootstrap.sh saga.
>
> On Thu, Jan 1, 2015 at 6:43 AM, Herbert Valerio Riedel
> wr
See https://github.com/haskell/cabal/issues/2310 for a continuation of the
sad bootstrap.sh saga.
On Thu, Jan 1, 2015 at 6:43 AM, Herbert Valerio Riedel wrote:
> On 2014-12-30 at 21:23:19 +0100, Jake Wheat wrote:
>
> [...]
>
> > Simplify the bootstrap.sh process:
> >
> > * always use a fixed set
On 2014-12-30 at 21:23:19 +0100, Jake Wheat wrote:
[...]
> Simplify the bootstrap.sh process:
>
> * always use a fixed set of versions of packages for the dependencies
For me, the primary use-case of `bootstrap.sh` is to be able to build a
matching `cabal-install` executable for a given major GH
I have some ideas about how to improve the bootstrap.sh situation.
Rewriting in haskell sounds like a good idea to avoid the shell script
mess.
Simplify the bootstrap.sh process:
* always use a fixed set of versions of packages for the dependencies
* always bootstrap in a sandbox, and ignore pac
Hi all,
I've spent more time on the bootstrap.sh script than anything else, making
it emulate cabal flag resolution for the network-uri split and make it deal
with the fact that network-uri makes Haddock choke. this release. That
feels like a somewhat wasteful activity and I'm tired of maintain a
