Christopher X. Candreva <[EMAIL PROTECTED]> wrote: > I believe this change is a mistake for two reasons. First, a web application > will often need special permissions on it's cache directory. [...] > The second problem was brought up on this list back in Aug, when someone > asked if the CACHEDIR.TAG file itself should be backed up even if the > contents aren't .
Yes, this is reasonable. On the other hand, however, there are cases when the directory presense in the archive is not needed at all. The CACHEDIR.TAG specification itself does not specify whether the directory itself should or should not be backed up. We could provide a finer control of what --exclude-caches and --exclude-tag options, for example: --exclude-caches Excludes the contents of the directory where CACHEDIR.TAG is found, but preserves both the directory itself and CACHEDIR.TAG --exclude-caches-file Excludes the contents of the directory where CACHEDIR.TAG, but preserves the directory itself --exclude-caches-all Excludes the contents of the directory where CACHEDIR.TAG and the directory itself Similarly for --exclude-tag set of options: --exclude-tag=FILE --exclude-tag-file=FILE --exclude-tag-dir=FILE Opinions? Regards, Sergey
