Re: [Duplicity-talk] --include and --exclude questions

[Andrew Kohlsmith (lists)]

On June 5, 2008 10:21:41 pm Jacob wrote:
> I can answer this part. You probably already know that, at the first
> include or exclude that matches, duplicity no longer moves forward and
> either includes or excludes as specified. Take the /mnt/data/var/www/site1
> folder as an example:
>
> (no match)    --include /etc
> (no match)    --include /home
> (no match)    --include /mnt/data/usrlocal/scripts
> (no match)    --include /mnt/data/var/data
> (no match)    --include /mnt/data/var/spool
> (is match)    --include /mnt/data/var/www
> (skipping)    --exclude /mnt/data/var/www/site1
> (skipping)    --exclude /mnt/data/var/www/site2
> (skipping)    --exclude /mnt/data/var/data/duplicity
> (skipping)    --exclude '**'
>
> As you can see, the --exclude rule for /mnt/data/var/www matches at least
> part of /mnt/data/var/www/site1. The best option would be to have the
> specific excludes first, includes later, then the "**" exclude last to
> catch all else.

Ahh, okay, it stops at the first match.  I got it now.  I tried using globbing 
filelists (Edgar's suggestion) in the same order as above, with the same 
results. 

I'll put the more specific ones first.  In a way it makes sense, but at the 
same time it doesn't.  :-)  Thank you so much.

Regards,
Andrew