Since we changed the global cache location to ~/.cache/darcs/
and automatically consider ~/.darcs/cache as read-only (on linux
machines at least), we never really took advantage of the old,
read-only path.

This is because in the function copyFileUsingCache, we considered
~/.darcs/cache as a bucketed source (we used hashedFilePath instead
of hashedFilePathReadOnly). Also, copying some hashed file with
copyFileUsingCache always failed because after reading (and not
finding the file) in ~/.darcs/cache (which is the first read-only
location is the list of locations that the function usually gets),
we just terminate without scanning other read-only locations
(typically, the source repository location).

This patch fixes these two problems.

1 patch for repository http://darcs.net:

patch 4935db39c767f4bad771442fbe14a24601360b75
Author: Guillaume Hoffmann <guillaumh@gmail.com>
Date:   Mon Apr  6 19:00:09 ART 2015
  * correctly take advantage of read-only cache locations

Attachments

• correctly-take-advantage-of-read_only-cache-locations.dpatch
• patch-preview.txt
• unnamed

Self-accept (in 2.10 too).