A while back I argued that if the user had no ~/.darcs/sources, a
default one should be written for them, and Darcs should use
~/.darcs/cache.  This would mean that newbies get the benefit of a
cache.

Because I keep ~/.darcs under version control, and because my scripts
automatically prune unused files from ~/.cache/, I have set up the
following:

    mkdir ~/.cache/darcs
    echo cache:$HOME/.cache/darcs >~/.darcs/sources

However I find that Darcs is still using ~/.darcs/cache instead of (or
perhaps as well as) ~/.cache/darcs.  I don't want this; darcs should
only use ~/.darcs/cache if it has not been explicitly told to use
something else.

Sounds like a bug.  Is this something we could get a test case out of?

On Thu, Apr 09, 2009 at 11:42:39AM -0000, Eric Kow wrote:
> Sounds like a bug.  Is this something we could get a test case out
> of?

I think the problem is confusion / breach of expectations.

Even after you fix ~/.darcs/sources, any existing repositories will
still have the wrong cache directory listed in _darcs/prefs/sources.
So those repos continue to use the wrong cache dir.

On Sat, Apr 11, 2009 at 09:51:10 -0000, Trent Buck wrote:
> Even after you fix ~/.darcs/sources, any existing repositories will
> still have the wrong cache directory listed in _darcs/prefs/sources.
> So those repos continue to use the wrong cache dir.

Petr: how does this fit into the plans you worked out during the
sprint for dealing with _darcs/prefs/sources issues?

I hope I'll have it documented somewhere soon besides the wiki 
progress page.

I believe this is a duplicate of issue1210

Darcs has no business recording the global cache in a repository's
_darcs/prefs/sources (because anything it needs from global would be hard-linked
anyway, so anybody fetching from it could just fetch from there)