Hi,

I have been trying to run darcs-benchmark on some machines, and it has been
extraordinarily slow on our university machines with NFS-mounted homes. It took
a while to figure, that darcs is trying to access /home/eykk10/.darcs/cache all
the time, which does not exist and triggers automount every time, making darcs
wait on the order of a significant fraction of a second for *every patch it
tries to process*.

I have no idea why is the global cache being recorded in _darcs/, but that is
almost certainly a bug -- if user disables global cache in ~/.darcs/, they also
likely don't want it to be still used by all their existing repos...

I am filing this so that we don't forget to fix this for 2.2. I'll try to
followup with some patches when I get around to it...

Yours,
   Petr.

I agree that this is not as one would expect.
But it is consistent with documentation.

Did you add cache to your .darcs/sources file only?

Didn't get around to do that and time's almost out for 2.2. Let's bump this to 
2.3.

Bump to Darcs 2.4?

Bumped indefinitely, as it is appears not to be going in in time for 2.4.

The following patch updated the status of issue1210 to be resolved:

* Resolve issue1210: global cache gets recorded in _darcs/prefs/sources 
Ignore-this: 5e7d0c93f25b2b64b949e66fc0f17398

The following patch updated issue issue1210 with status=resolved;resolvedin=2.5.0 (current)

* Resolve issue1210: global cache gets recorded in _darcs/prefs/sources 
Ignore-this: 5e7d0c93f25b2b64b949e66fc0f17398