As if to demonstrate my earlier point, the new mechanism with wget
failed on me right away.
I have no idea what's going wrong. I set http_proxy, as I need to do
that for darcs anyway and I guess wget should pick that up, too. In
any case, I'm not keen on debugging this. There is no point in making
the whole system more complex and to introduce more failure points by
using wget in darcs-all. Can you please back that change out again?
Thanks,
Manuel
PS: I stop the d/l attempt here with Ctrl-C after a few tries, but
they go on and on if I let them.
limitingfactor chak 6 (.../Code/ghc-test): env LANG=C ./darcs-all get
warning: adding --partial, to override use --complete
warning: . already present; omitting
warning: utils/hsc2hs already present; omitting
warning: utils/haddock already present; omitting
warning: libraries/array already present; omitting
warning: libraries/base already present; omitting
warning: libraries/binary already present; omitting
warning: libraries/Cabal already present; omitting
warning: libraries/containers already present; omitting
warning: libraries/directory already present; omitting
warning: libraries/dph already present; omitting
warning: libraries/extensible-exceptions already present; omitting
warning: libraries/filepath already present; omitting
warning: libraries/ghc-prim already present; omitting
warning: libraries/haskeline already present; omitting
warning: libraries/haskell98 already present; omitting
warning: libraries/hpc already present; omitting
warning: libraries/integer-gmp already present; omitting
warning: libraries/integer-simple already present; omitting
warning: libraries/mtl already present; omitting
warning: libraries/old-locale already present; omitting
warning: libraries/old-time already present; omitting
warning: libraries/pretty already present; omitting
warning: libraries/process already present; omitting
warning: libraries/random already present; omitting
warning: libraries/template-haskell already present; omitting
warning: libraries/terminfo already present; omitting
warning: libraries/unix already present; omitting
warning: libraries/utf8-string already present; omitting
warning: libraries/Win32 already present; omitting
== Syncing tarballs
== running wget darcs.haskell.org:/home/darcs/ghc-tarballs/gcc-
core-3.4.5-20060117-3.tar.gz -O mingw/gcc-core-3.4.5-20060117-3.tar.gz
--2009-10-22 11:20:32--
ftp://darcs.haskell.org//home/darcs/ghc-tarballs/gcc-core-3.4.5-20060117-3.tar.gz
=> `mingw/gcc-core-3.4.5-20060117-3.tar.gz'
Resolving darcs.haskell.org... 69.30.63.197
Connecting to darcs.haskell.org|69.30.63.197|:21... failed:
Operation timed out.
Retrying.
--2009-10-22 11:21:48--
ftp://darcs.haskell.org//home/darcs/ghc-tarballs/gcc-core-3.4.5-20060117-3.tar.gz
(try: 2) => `mingw/gcc-core-3.4.5-20060117-3.tar.gz'
Connecting to darcs.haskell.org|69.30.63.197|:21... failed:
Operation timed out.
Retrying.
--2009-10-22 11:23:05--
ftp://darcs.haskell.org//home/darcs/ghc-tarballs/gcc-core-3.4.5-20060117-3.tar.gz
(try: 3) => `mingw/gcc-core-3.4.5-20060117-3.tar.gz'
Connecting to darcs.haskell.org|69.30.63.197|:21... failed:
Operation timed out.
Retrying.
--2009-10-22 11:24:23--
ftp://darcs.haskell.org//home/darcs/ghc-tarballs/gcc-core-3.4.5-20060117-3.tar.gz
(try: 4) => `mingw/gcc-core-3.4.5-20060117-3.tar.gz'
Connecting to darcs.haskell.org|69.30.63.197|:21... ^Cwget failed: 2
== Checking for old bytestring repo
limitingfactor chak 7 (.../Code/ghc-test):
Am 22/10/2009 um 10:34 schrieb Manuel M T Chakravarty:
Malcolm Wallace:
If you are using msys, then you can get a wget program by ...
Just wanted to point out that MacOS X does not by default supply
wget either (although it does have curl).
That's right. I think it is a bad idea to require that wget is
available to get GHC. This comes back to the discussion about
making it easy for people to get GHC sources, to build the system,
and to contribute. Every additional application that you require
people to install before they can join into the fun will reduce the
number of people who will actually try.
If you want to download tarballs separately, then I think the GHC
tree must include an app (written in Haskell) to do that, which
means that whatever packages that app needs, need to go into the set
of boot libraries, which in turn is not desirable.
The simpler solution is probably to keep downloading tarballs via
darcs as before.
Manuel
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
