[tahoe-dev] [tahoe-lafs] #705: "tahoe mv" unlinks the target even when it is a directory

[tahoe-lafs]

#705: "tahoe mv" unlinks the target even when it is a directory
-------------------------------+--------------------------------------------
 Reporter:  zooko              |           Owner:       
     Type:  defect             |          Status:  new  
 Priority:  critical           |       Milestone:  1.5.0
Component:  code-frontend-cli  |         Version:  1.4.1
 Keywords:  reliability        |   Launchpad_bug:       
-------------------------------+--------------------------------------------

Comment(by warner):

 Hm, good question. "tahoe mv" was indeed meant for tahoe-to-tahoe moves,
 so that an unqualified "file1" really means "tahoe:file1". (the fact that
 "tahoe mv alias:file1 alias:file1" results in deleting a file is certainly
 a bug, probably in the dirnode code).

 I don't know if it's better to add docs/etc to teach people to expect that
 "tahoe mv" doesn't touch the local disk, or to add code/tests to make
 "tahoe mv" behave more like people's existing expectations. There's value
 in having all tahoe CLI commands that happen to overlap regular unix
 commands (cp, ln, mv, rm) be prepared to handle both local-disk and tahoe-
 filesystem arguments. But it also adds code, complication, and redundancy
 (e.g. why would you ever use "tahoe rm ~/.emacs" instead of regular rm?).

 Overall, I guess 'mv' should handle both local and tahoe-side files, and
 should behave like 'cp'.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/705#comment:10>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid