Opened at 2007-09-29T16:17:16Z

Closed at 2007-10-11T22:41:07Z

#154 closed defect (fixed)

usage string program name != executable name?

Reported by: zooko Owned by: nobody
Priority: minor Milestone: 0.6.1
Component: code-frontend Version: 0.6.0
Keywords: Cc:
Launchpad Bug:

Description

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".

Change History (3)

comment:1 Changed at 2007-09-29T16:28:04Z by zooko

  • Component changed from unknown to code-frontend
  • Owner changed from nobody to zooko
  • Status changed from new to assigned

comment:2 Changed at 2007-10-01T22:10:45Z by zooko

  • Owner changed from zooko to nobody
  • Status changed from assigned to new

comment:3 Changed at 2007-10-11T22:41:07Z by warner

  • Resolution set to fixed
  • Status changed from new to closed

fixed, in 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?

Note: See TracTickets for help on using tickets.