Nope, neither.
I'm wondering if it somehow isn't working by using the variable
$EXCLUDES?
It works without using this variable.
Also, there's this in the man page:
The --exclude pattern option matches a file iff:
.
pattern can be expanded into the file’s filename, or
.
the file is inside a directory matched by the option.
If so, how is one to exclude a directory? I want a blacklist, not a
whitelist.
Any ideas?
On Wed, Nov 24, 2010 at 5:38 PM, <address@hidden> wrote:
On 24.11.2010 18:01, Chris Poole wrote:
Just one more thing then. I'm not sure why this isn't working,
perhaps you
do?
DRIVENAME='offsite1'
INCLUDES=''
EXCLUDES="--exclude ~/.cache --exclude ~/Library/Caches
--exclude
~/Dropbox --exclude ~/test --exclude ~/src --exclude ~/Downloads
--exclude ~/Public --exclude ~/Sites --exclude '**/.DS_Store'"
duplicity $INCLUDES $EXCLUDES ~/
"file:///Volumes/$DRIVENAME/backup/"
I get the message:
Fatal Error: The file specification
~/.cache
cannot match any files in the base directory
/Users/Chris
Now, I can use the glob **, to give **/.cache in the EXCLUDES
variable, but then won't this match any .cache directory,
regardless
of depth? (I just want to match the ~/.cache directory explicitly).
how about './.cache' or simply '.cache' ?
as ~ is probably your backup source root.
ede/duply.net
_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk
_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk