[tahoe-lafs-trac-stream] [tahoe-lafs] #835: "tahoe cp -r --mutable": make mutable copy of immutable directories, vice versa

tahoe-lafs trac at tahoe-lafs.org
Sat Nov 26 14:00:29 UTC 2011


#835: "tahoe cp -r --mutable": make mutable copy of immutable directories, vice
versa
-----------------------------------+--------------------------------
     Reporter:  warner             |      Owner:
         Type:  enhancement        |     Status:  new
     Priority:  major              |  Milestone:  soon
    Component:  code-frontend-cli  |    Version:  1.5.0
   Resolution:                     |   Keywords:  usability tahoe-cp
Launchpad Bug:                     |
-----------------------------------+--------------------------------
Changes (by davidsarah):

 * cc: kpreid (added)


Comment:

 Kevin Reid [https://tahoe-lafs.org/pipermail/tahoe-
 dev/2011-November/006860.html wrote on tahoe-dev]:
 > I want to experiment with running a webapp off a Tahoe grid. It would
 handle its own "database" read/write, but I need to bootstrap same-origin
 by uploading its source files to the grid.
 >
 > 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.
 >
 > I suppose '{{{tahoe cp}}}' is the closest in function I have found, but
 all else being equal I would like to have my 'install' function not
 actually use any of the user's pre-existing Tahoe capabilities. I could
 '{{{tahoe mkdir}}}' a fresh directory and cp into it.
 >
 > Any suggestions on how to do this more cleanly?

 As well as the functionality of the proposed {{{tahoe cp --immutable}}},
 Kevin's post also mentions exclusions, similar to {{{tahoe backup}}}'s
 {{{--exclude*}}} options I assume. I've filed as #1597 to make {{{tahoe
 cp}}} support those options.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/835#comment:8>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list