For the purpose of experimenting with NDP I went through the process of getting the GHC head from darcs.haskell.org. As specified in the developer wiki[1], using darcs get is basically not possible because there're so many patches. So I downloaded http://darcs.haskell.org/ghc-HEAD-2008-06-06-ghc-corelibs-testsuite.tar.bz2 This alone took over *7 hours* using wget because it could never get a connection faster than 5kb/s. After downloading I changed to the directory and ran 'darcs pull -a'. Nothing bad happened here, darcs pulled most of the changes pretty quick so I had an up to date GHC. However, when trying to use the ./darcs-all script to pull in the latest library/testsuite changes, things go horribly, horribly wrong. I let darcs sit for over another hour and a half trying to pull patches from darcs.haskell.org for the libraries and the testsuite. It never got past packages/base. In fact, it never even got to *getting* the patches from the base repository, it sat there, stuck at the 'identifying repository' stage (darcs 2.0.2) for over an hour, making my processor go round and round at 99% CPU usage the entire way, never accomplishing anything. What makes it even stranger is that it got the latest patches for the testsuite and the array package pretty quick. It just got permanently stuck on base for some reason and never went further. Also, I tried pulling package-ndp a few days ago while using an older development snapshot of GHC (not the darcs repository, a nightly HEAD tarball of ghc.) Just pulling 500 patches from http://darcs.haskell.org/packages/ndp took over an hour, but at least it got done. It didn't build properly so I thought I'd get the latest darcs version of GHC instead, and here I am. Has anybody experienced anything like this recently? Off the top of my head the only things that possibly come to mind are: 1) darcs.haskell.org is just really slow or under -constant- heavy load. 2) the darcs repositories are in darcs-1 format, so darcs-2 is having issues when trying to pull the patches. 3) Diabolical connection-killing ninjas. None of these 3 possibilities are really 'great,' and none of them help me get the latest version of GHC, the libs, and NDP any faster then a narcoleptic snail. If instead this is a techincal issue with, say, darcs that someone is aware of, I'm using OS X Leopard, 10.5.4 with a statically linked darcs-2.0.2 binary from [2]. [1] http://hackage.haskell.org/trac/ghc/wiki/Building/GettingTheSources [2] http://wiki.darcs.net/DarcsWiki/CategoryBinaries#head-25c8108e9d719be30a8cc6...