[tahoe-lafs-trac-stream] [tahoe-lafs] #712: tahoe cp flattens directories

tahoe-lafs trac at tahoe-lafs.org
Fri Aug 2 18:26:13 UTC 2013


#712: tahoe cp flattens directories
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:  daira
         Type:  defect   |     Status:  assigned
     Priority:  major    |  Milestone:  1.11.0
    Component:  code-    |    Version:  1.4.1
  frontend-cli           |   Keywords:  tahoe-cp usability recursive test-
   Resolution:           |  needed
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by markberger):

 This error doesn't occur when `./` is supplied instead of `*`.

 I believe this ticket ultimately arises from tahoe's interface design and
 not necessarily from a bug in the code. Because `tahoe cp` can take
 multiple arguments, `*` is supplying both files and directories. The CLI
 breaks down the list of arguments into individual copy actions, so each
 folder and file can be viewed to have its own `tahoe cp` call.

 In the instance of `tahoe cp -r example_dir/ tahoe:example_dir/`, the
 contents of example_dir/ should be placed into tahoe:example_dir/ without
 preserving the top level directory (by this I mean we want
 tahoe:example_dir/contents, not tahoe:example_dir/example_dir/contents).

 However with this ticket, we want the opposite behavior. By supplying `*`,
 we are telling tahoe to copy multiple directories to the grid, but in this
 instance we want to retain the top level directory (we want tahoe to
 create tahoe:example_dir/example_dir/ if example_dir/ is in *).

 In order to have the desired behavior outlined in this ticket, we need to
 distinguish between these two scenarios. I believe the current behavior
 makes sense, although it is counter intuitive to what users probably
 expect. I'm not sure how we can distinguish between these two behaviors
 while keeping support for multiple arguments since it seems like `*` is
 populated by the console (I could be wrong about this).

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


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