I welcome the addition of a configuration file in 3.2, but that file is located in a directory with a cache directory tag, so systems are free to blow it away, and backup software is encouraged not to back it up. That seems bad. I suggest an approach along the lines of bug 10383, using the XDG system to locate the various "dot" directories and files.
> I welcome the addition of a configuration file in 3.2, but that file is located > in a directory with a cache directory tag, so systems are free to blow it away, > and backup software is encouraged not to back it up. That seems bad. Yes, that's unfortunate, thanks for the bug report. My suggested fix for this is to create CACHEDIR.TAG files in the $CCACHE_DIR/[0-9a-f] directories instead of directly in $CCACHE_DIR. Does that seem OK? > I suggest an approach along the lines of bug 10383, using the XDG system to > locate the various "dot" directories and files. As mentioned in bug 10383, I've come to the conclusion that I don't think that's a good idea.
Fixed in ed51f2b56ec81b924bbc172715458bbce682e863 on 3.2-maint.
Included in v3.2.1.