[tahoe-lafs-trac-stream] [tahoe-lafs] #166: command line order is problematic

tahoe-lafs trac at tahoe-lafs.org
Fri Jun 15 01:39:35 UTC 2012


#166: command line order is problematic
-------------------------+-------------------------------------------------
     Reporter:  zandr    |      Owner:  zooko
         Type:  defect   |     Status:  new
     Priority:  major    |  Milestone:  1.10.0
    Component:  code-    |    Version:  0.6.1
  frontend-cli           |   Keywords:  security usability unix mac error
   Resolution:           |  review-needed zookos-opinion-needed
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by warner):

 latest patch (also visible in https://github.com/warner/tahoe-
 lafs/tree/166-args) fixes the first issue (mentioning global options)

 So the remaining question is {{{-d}}} before the subcommand. I'm not
 hugely motivated to make it possible to write new scripts that work with
 old versions (unlike py2/py3 I think once you've upgrated to a new tahoe
 version, you'll just stick with it). And I prefer the simplicity of having
 fewer options (I still want to remove the {{{-C/--basedir}}} option from
 the node-admin commands, but want to respect David-Sarah's opinion that
 people may have scripts that will break).

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


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