[tahoe-dev] tahoe -d is awkward
David-Sarah Hopwood
david-sarah at jacaranda.org
Thu May 12 07:53:08 PDT 2011
On 11/05/11 21:50, Brian Warner wrote:
> The only reason I didn't put -d on the top-level options parser was
> because there are several commands that don't use it. But at this point,
> those commands are in the minority (just the 'tahoe debug' subcommands,
> like 'tahoe debug dump-share' and 'tahoe debug trial'), and they can
> just ignore the option.
They already do. -d is in BaseOptions (in src/allmydata/scripts/common.py)
since <http://tahoe-lafs.org/trac/tahoe-lafs/changeset/4614/trunk>,
released in Tahoe-LAFS v1.8.
> For compatibility with folks' existing scripts, both the main command
> and the subcommand should accept -d.
I don't understand why that's needed.
The default node directory is given by get_default_nodedir in common.py
<http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/src/allmydata/scripts/common.py#L10>.
--
David-Sarah Hopwood ⚥ http://davidsarah.livejournal.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 294 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110512/e7f8b0f2/attachment.pgp>
More information about the tahoe-dev
mailing list