I think the tag issue is available nowadays via --exclude-caches and adding CACHEDIR.TAG files which conform to http://www.brynosaurus.com/cachedir/spec.html
However I still think obnam needs more flexible excluding options. In particular: -the ability to INCLUDE files to backup via config files, with such inclusions taking precedence over all stated exclusions. This would allow blanket exclusion of a hierarchy, with specified exceptions. For example, "^/all/, !^/all/except-that" would skip /all/* but not /all/except-that -obnam reads in multiple .conf files (if present in /etc/obnam/ or ~/.config/obnam/) but the exclude options in such files clobber each other: the last one read in, wins. This prevents me from having the same generic exclusion list on several machines, complemented by a local exclusion list, for example. It would be better if an exclude option in a later file would add to, rather than replace, exclude options in earlier config files. Cheers! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
