[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2404: optionally backup to mutable files/directories (was: optionally backup to mutable directory)

[Tahoe-LAFS]

#2404: optionally backup to mutable files/directories
-----------------------------+-----------------------
     Reporter:  lpirl        |      Owner:
         Type:  enhancement  |     Status:  new
     Priority:  normal       |  Milestone:  undecided
    Component:  unknown      |    Version:  1.10.0
   Resolution:               |   Keywords:
Launchpad Bug:               |
-----------------------------+-----------------------
Changes (by lpirl):

 * cc: tahoe-lafs.org@… (added)
 * type:  defect => enhancement


Old description:

> From my understanding, when using `tahoe backup` it is currently not
> possible to have ''a single'' CAP always pointing to the latest snapshot
> (wording with respect to #1952).
>
> Is there a specific reason why the directory `Latest` is immutable?
> If so, `tahoe backup` could have an additional switch to use a mutable
> directory.
> If not, `tahoe backup` could use a mutable directory per default.

New description:

 From my understanding, when using `tahoe backup` it is currently not
 possible to have ''a single'' CAP always pointing to the latest version of
 a file/directory.

 Couldn't `tahoe backup` put an immutable, timestamped copy of `Latest`
 into `Archives` and update everything in `Latest` afterwards?
 That way, `Latest` would contain only CAPs that (are not changing and) are
 always pointing to the most recent version of a file/direcory.

--

Comment:

 I just realized that this can be seen much more general and updated the
 ticket accordingly.

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