[tahoe-dev] How do I do an immutable tree upload?

[David-Sarah Hopwood]

On 26/11/11 17:15, David-Sarah Hopwood wrote:
> On 26/11/11 14:30, Greg Troxel wrote:
>>
>>   It seems to me that the right thing here is a command which will
>>   upload the entire file tree (preferably with exclusions) immutably (to
>>   minimize duplication when I upload with changes) and return a dircap
>>   for it. What 'tahoe' arguments will do this?
>>
>>   'tahoe cp' requires a target directory and does not appear to produce
>>   immutable directories. 'tahoe put' does not appear to do
>>   directories. 'tahoe backup' requires a target directory and keeps old
>>   versions.
>>
>> Not what you asked, but to me this is a symptom of "mounting taho as a
>> filesystem is not the standard approach".  You are using tahoe as a
>> filesystem and then struggling with the not-quite-standard-filesystem
>> tools that are available, rather than mounting it and just using rsync
>> or cp -R, much like you would put content on any other filesystem.
> 
> Hmm? Since most filesystems don't have immutable files or directories,
> that would make the requested feature more difficult to implement (than,
> for example, the proposed 'tahoe -r --immutable'), not less.

'tahoe cp -r --immutable', I meant.

-- 
David-Sarah Hopwood ⚥ http://davidsarah.livejournal.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 294 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20111126/db8e0231/attachment.pgp>