[tahoe-lafs-trac-stream] [tahoe-lafs] #1359: tahoe cp --help gives incorrect placement of [options], and [options] is missing in other synopses
tahoe-lafs
trac at tahoe-lafs.org
Wed Jul 27 13:11:07 PDT 2011
#1359: tahoe cp --help gives incorrect placement of [options], and [options] is
missing in other synopses
---------------------------------+-----------------------------------------
Reporter: killyourtv | Owner: davidsarah
Type: defect | Status: new
Priority: minor | Milestone: 1.9.0
Component: code-frontend- | Version: 1.8.2
cli | Keywords: tahoe-cp help easy reviewed
Resolution: |
Launchpad Bug: |
---------------------------------+-----------------------------------------
Changes (by zooko):
* keywords: tahoe-cp help easy review-needed => tahoe-cp help easy
reviewed
* owner: => davidsarah
Comment:
It looks like in attachment:fix-cli-synopses-2.darcs.patch it ''does''
change the command name to a hardcoded {{{tahoe}}} if {{{argv[0]}}}
suggests {{{trial}}}. Is that intentional? I don't mind too much either
way. Note that there is an "application name" which is [http://tahoe-
lafs.org/trac/tahoe-
lafs/browser/trunk/setup.py?annotate=blame&rev=5071#L41 produced by the
build system] and written into {{{src/allmydata/_appname.py}}}, in a
similar vein to the way the version number is produced by the build system
and written into {{{src/allmydata/_version.py}}}, but there is not
currently an ''executable name'' that is produced by the build system. One
could imagine the build system producing an executable name, such as by
writing it into {{{src/allmydata/_execname.py}}}, and then all the places
in the code, including this place, which need to use an executable name
could refer to that.
(New ticket?)
Other than that, {{{+1}}} on this patch! Please apply.
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1359#comment:6>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list