Comment 1 for bug 1408411

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

I note that this was explicitly flagged in the manual (see point 2):
"The --include-filelist, --exclude-filelist, --include-filelist-stdin, and --exclude-filelist-stdin options also introduce file selection conditions. They direct duplicity to read in a file, each line of which is a file specification, and to include or exclude the matching files. Lines are separated by newlines or nulls, depending on whether the --null-separator switch was given. Each line in a filelist is interpreted similarly to the way extended shell patterns are, with a few exceptions:

1. Globbing patterns like *, **, ?, and [...] are not expanded.
2. Include patterns do not match files in a directory that is included. So /usr/local in an include file will not match /usr/local/doc. #
"

But I maintain that this should be changed. It seems a bizarre distinction to have between normal and globbing filelists. There is some risk that changing this could mean users have additional subfolders backed up that were not previously included, but this seems less of an issue than the potential that desired subfolders are mistakenly excluded.