#839: Copying directories containing caps from the future
-----------------------------------+----------------------------------------
Reporter: davidsarah | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Component: code-frontend-cli | Version: 1.5.0
Keywords: forward-compatibility | Launchpad_bug:
-----------------------------------+----------------------------------------
Comment(by davidsarah):
If we add a "copyByReference" flag, which controls whether a directory
entry with an unknown cap format is copied just by copying its
representation, then we can defer the decision as to which caps are copied
in that way to when the new cap formats are designed.
It would also be possible to add a field giving the lowest Tahoe version
that fully supports that cap format. So when you operate on a directory
with unknown caps, it would find the maximum unknown version, x.y.z, and
print something like "Some entries in this directory are not supported by
the current version of Tahoe. The creator of one or more of these entries
claimed that Tahoe version x.y.z is needed."
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/839#comment:2>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
_______________________________________________
tahoe-dev mailing list
[email protected]
http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
