cli: to specify basedir sometimes requires "-C" option, other times just an argument #772

New Issue

tahoe-lafs · 2009-07-25T14:10:06Z

robk commented

2009-07-25 14:10:06 +00:00

while you can say "tahoe create-introducer introducer"

it is an error to say "tahoe create-key-generator key-generator"
the latter requires the -C flag. a little more consistency would be nice.

while you can say "tahoe create-introducer introducer" it is an error to say "tahoe create-key-generator key-generator" the latter requires the -C flag. a little more consistency would be nice.

tahoe-lafs added the

labels 2009-07-25 14:10:06 +00:00

tahoe-lafs added this to the undecided milestone 2009-07-25 14:10:06 +00:00

zooko commented

2009-07-25 14:17:17 +00:00

This was previously mentioned in #188 (--basedir vs. --node-directory), but it is better to have a separate ticket for this, so this is now the official ticket for this issue.

zooko added

code-frontend-cli

and removed

unknown

labels 2009-07-25 14:17:17 +00:00

zooko changed title from ~~tahoe create-key-generator requires -C~~ to cli: to specify basedir sometimes requires "-C" option, other times just an argument

2009-07-25 14:17:17 +00:00

davidsarah commented

2010-01-12 05:00:51 +00:00

I will fix this together with #188.

tahoe-lafs modified the milestone from undecided to 1.6.0

2010-01-12 05:00:51 +00:00

zooko modified the milestone from 1.6.0 to eventually

2010-01-26 15:38:17 +00:00

tahoe-lafs modified the milestone from eventually to 1.7.0

2010-02-01 19:42:31 +00:00

JeremyVisser commented

2010-03-09 06:50:50 +00:00

I was a little confused by the fact that '-C' is sometimes optional. For example, 'tahoe start .' and 'tahoe start -C .' are synonymous.

Best to have complete consistency, IMO.

I was a little confused by the fact that '-C' is sometimes optional. For example, 'tahoe start .' and 'tahoe start -C .' are synonymous. Best to have complete consistency, IMO.

tahoe-lafs modified the milestone from 1.7.0 to 1.7.1

2010-06-12 21:09:17 +00:00

tahoe-lafs modified the milestone from 1.7.1 to 1.8β

2010-07-17 04:23:33 +00:00

davidsarah commented

2010-07-22 02:10:28 +00:00

With the patch attached to #715, "tahoe create-key-generator keygeneratordir" now works.

With the patch attached to #715, "`tahoe create-key-generator keygeneratordir`" now works.

david-sarah@jacaranda.org commented

2010-08-02 04:49:34 +00:00

In [4614/ticket798]:

Basedir/node directory option improvements for ticket798 branch. addresses #188, #706, #715, #772, #890

In [4614/ticket798]: ``` Basedir/node directory option improvements for ticket798 branch. addresses #188, #706, #715, #772, #890 ```

davidsarah commented

2010-08-08 01:05:30 +00:00

Applied to trunk in changeset:f952532f0822fbe7 changeset:54a9ba8232e2b8e9 changeset:a7c474a09893b9aa. NEWS changes were in changeset:0ae556c00ac79d4f changeset:2b15f35b867cebbd.

This ended up also allowing tahoe create-key-generator --multiple ..., not because it's especially useful but because it was implied by using the same code for all create-* commands.

Applied to trunk in changeset:f952532f0822fbe7 changeset:54a9ba8232e2b8e9 changeset:a7c474a09893b9aa. NEWS changes were in changeset:0ae556c00ac79d4f changeset:2b15f35b867cebbd. This ended up also allowing `tahoe create-key-generator --multiple ...`, not because it's especially useful but because it was implied by using the same code for all `create-*` commands.

tahoe-lafs added the

fixed

label 2010-08-08 01:05:30 +00:00

tahoe-lafs closed this issue

2010-08-08 01:05:30 +00:00

Sign in to join this conversation.