tahoe-lafs/trac-2024-07-25

usage string program name != executable name? #154

New issue

Closed

opened 2007-09-29 16:17:16 +00:00 by zooko · 1 comment

zooko commented

2007-09-29 16:17:16 +00:00

Owner

Sebastian tried out Tahoe last night, and one thing he pointed out was that the file he executed was named "allmydata-tahoe", but the usage string suggested that it be invoked as "allmydata".

Sebastian tried out Tahoe last night, and one thing he pointed out was that the file he executed was named "allmydata-tahoe", but the usage string suggested that it be invoked as "allmydata".

tahoe-lafs added the

labels 2007-09-29 16:17:16 +00:00

tahoe-lafs added this to the 0.6.1 milestone 2007-09-29 16:17:16 +00:00

tahoe-lafs added

and removed

labels 2007-09-29 16:28:04 +00:00

warner commented

2007-10-11 22:41:07 +00:00

Author

Owner

fixed, in changeset:1c7f52265f0e7a38. The name 'allmydata' is still present in the output of
'tahoe --version':

% ./bin/tahoe --version
Twisted version: 2.5.0
Foolscap version: 0.1.7
zfec version: 1.1
allmydata version: 0.6.0-53

I'm not sure whether to change that or not.. the name of the python package
is still 'allmydata', so referring to "allmydata version" is slightly more
accurate than making it say "tahoe version". But the version string does
match the "allmydata-tahoe" source tarballs that we ship.

thoughts?

fixed, in changeset:1c7f52265f0e7a38. The name 'allmydata' is still present in the output of 'tahoe --version': ``` % ./bin/tahoe --version Twisted version: 2.5.0 Foolscap version: 0.1.7 zfec version: 1.1 allmydata version: 0.6.0-53 ``` I'm not sure whether to change that or not.. the name of the python package is still 'allmydata', so referring to "allmydata version" is slightly more accurate than making it say "tahoe version". But the version string *does* match the "allmydata-tahoe" source tarballs that we ship. thoughts?

tahoe-lafs added the

label 2007-10-11 22:41:07 +00:00

warner closed this issue

2007-10-11 22:41:07 +00:00

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#154

No description provided.