[tahoe-lafs-trac-stream] [Tahoe-LAFS] #851: tahoe backup exclude option only matches on filename instead of path

[Tahoe-LAFS]

#851: tahoe backup exclude option only matches on filename instead of path
-----------------------------------+------------------------------------
     Reporter:  francois           |      Owner:
         Type:  enhancement        |     Status:  new
     Priority:  major              |  Milestone:  eventually
    Component:  code-frontend-cli  |    Version:  1.5.0
   Resolution:                     |   Keywords:  tahoe-backup usability
Launchpad Bug:                     |
-----------------------------------+------------------------------------

Old description:

> The current implementation of --exclude for the 'tahoe backup' command
> only matches on filename instead of the full path to the file.
>
> Given the following filesystem hierarchy:
>
> {{{
> /dir1
> /dir1/file2
> /dir1/file1
> /dir2
> /dir2/dir1
> /dir2/dir1/file3
> }}}
>
> It is currently impossible to backup '/dir1' and NOT backup '/dir2/dir1'.
> The opposite, ie. to backup '/dir2/dir1' and NOT backup '/dir1' is also
> impossible.

New description:

 The current implementation of --exclude for the 'tahoe backup' command
 only matches on filename instead of the full path to the file.

 Given the following filesystem hierarchy:

 {{{
 /dir1
 /dir1/file2
 /dir1/file1
 /dir2
 /dir2/dir1
 /dir2/dir1/file3
 }}}

 It is currently impossible to backup '/dir1' and NOT backup '/dir2/dir1'.
 The opposite, ie. to backup '/dir2/dir1' and NOT backup '/dir1' is also
 impossible.

--

Comment (by daira):

 An S4 customer expressed an interest in being able to exclude directories,
 which could be done more reliably (not just by name) if this ticket were
 fixed.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/851#comment:4>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage