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

[tahoe-lafs]

#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 zooko):

 Replying to [comment:27 warner]:
 > 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).

 FWIW, I would prefer that simplicity too. I think Tahoe-LAFS currently has
 too much complexity in various ways, but one of those ways is the command-
 line syntax. I don't know whether anyone has scripts that would break, and
 if they do, maybe it would be not a big deal for them to detect the
 breakage and update their scripts. David-Sarah: is there any process by
 which we can prune old or redundant command-line syntax with sufficient
 grace period? Is it worth the effort to emit a "deprecation warning" sort
 of thing for options that we would like to remove in the future?

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