patch applied (packages/regex-base): Make setup script compileagain after recent Cabal changes

Sven Panne sven.panne at
Sat Sep 8 07:12:04 EDT 2007

On Thursday 06 September 2007 12:14, Simon Marlow wrote:
> Ian Lynagh wrote:
> > By the way, if you're currently pulling over SSH then you'll probably
> > find it much faster to pull over HTTP. [...]
> And it's dead easy to have a local repo tree that is kept up to date by a
> cron job.  A 'darcs-all pull -a' from the local tree then takes only a few
> seconds.

Ummm... Now I'm completely confused, perhaps I'm using darcs in a suboptimal 
way. Anyway, let's not forget the small minority of people at home behind 
something slower than T1, which like to switch off their boxes from time to 
time... (including me ;-) My usage scenario is still the same as it has been 
for lots of years:

   * I work on GHC from home.

   * My computer is not running 24/7, therefore everyhing cron-lilke is a 

   * I'm behind something reasonably fast for home purposes (currently 2Mbit/s 

   * I need all of GHC + extralibs.

   * Non-partial darcs repositories seem to be necessary for development to 
keep oneself in a sane state of mind.

   * I need to be able to push my changes to (possible via 
SSH only, I guess).

To work like this, I did the obvious (at least obvious for me): "darcs get" 
full repositories via SSH (a Herculean effort, lasting more than half a day), 
synching everything via "darcs-all pull" (i.e. effectively via SSH, taking 
about 20min), pushing via plain "darcs push" (i.e. SSH again, not fast, but 
bearable). Is there anything wrong with that? Hints?


More information about the Libraries mailing list