GHC MinGW distribution

[Edsko de Vries]

git-annex (written in Haskell!) is designed specifically for this purpose.
might be worth a look.

-E


On Tue, Jun 10, 2014 at 4:02 PM, Simon Peyton Jones <simonpj at microsoft.com>
wrote:

> | Right now, cloning the ghc-tarballs.git repo requires to fetch ~130MiB.
> |
> | Can't we simply put the tarballs in a plain HTTP folder on
> | http://ghc.haskell.org, and store a list (or rather a shell script) of
> | URLs+checksums in ghc.git to retrieve the tarballs if needed on demand?
>
> Personally I'm fine with that, if someone feels able to implement it (and
> document in the wiki:Repositories page).
>
> But remember that I'm not very au fait with all the issues so I defer to
> others
>
> Simon
>
> | -----Original Message-----
> | From: Herbert Valerio Riedel [mailto:hvriedel at gmail.com]
> | Sent: 10 June 2014 09:43
> | To: Simon Peyton Jones
> | Cc: Robin KAY; ghc-devs at haskell.org
> | Subject: Re: GHC MinGW distribution
> |
> | Hello Simon,
> |
> | On 2014-06-10 at 10:25:46 +0200, Simon Peyton Jones wrote:
> |
> | [...]
> |
> | > We physically include very selective chunks of MinGW in a GHC Windows
> | distribution
> | > - so that users don't need to install MinGW
> | > - so that GHC doesn't break just because a user has
> | >   a different version of MinGW than we expected
> | > We keep these chunks of MinGW in the GHC repo (in ghc-tarballs)
> | > precisely so that we know exactly which bits to ship.
> |
> | Btw, there's just one thing I'm worried about with keeping those large
> | MinGW binary tarballs in a Git repo:
> |
> | The Git repo will grow monotonically with each new compressed
> | .tar.{bz2,lzma,gz,...} added, with little opportunity for Git to detect
> | shared bitstreams. So effectively each MiB of binary-data added will
> | effectively grow the Git repo everyone will have to clone (even if only
> | the latest MinGW for a specific 32/64-bit platform is desired) by that
> | same amount.
> |
> | Right now, cloning the ghc-tarballs.git repo requires to fetch ~130MiB.
> |
> | Can't we simply put the tarballs in a plain HTTP folder on
> | http://ghc.haskell.org, and store a list (or rather a shell script) of
> | URLs+checksums in ghc.git to retrieve the tarballs if needed on demand?
> |
> | Cheers,
> |   hvr
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20140611/a732b24a/attachment.html>