[tahoe-dev] [tahoe-lafs] #652: "appname" in version shouldn't change keys of "tahoe --version"

tahoe-lafs trac at allmydata.org
Wed Mar 4 14:38:17 PST 2009


#652: "appname" in version shouldn't change keys of "tahoe --version"
-----------------------+----------------------------------------------------
 Reporter:  warner     |           Owner:  somebody 
     Type:  defect     |          Status:  new      
 Priority:  major      |       Milestone:  undecided
Component:  packaging  |         Version:  1.3.0    
 Keywords:             |   Launchpad_bug:           
-----------------------+----------------------------------------------------
 When Zandr was merging the recent 1.3.0 release into his "tahoe-server"
 branch, he had to do a global-search-and-replace of "allmydata-tahoe" with
 "tahoe-server". Unfortunately it looks like this also affects the output
 of "tahoe --version" in a negative way: the "key" (i.e. the thing on the
 left side of the colon) changes. The relevant part of the output goes
 from:

 {{{allmydata-tahoe: 1.3.0-r5678}}}

 to:

 {{{tahoe-server: 1.3.0-r1234}}}

 Likewise, the version dictionary that {{{flogtool tail}}} retrieves sees a
 new key name. I seem to recall that there were some other places which
 were affected that I'd prefer were not, but I don't remember which ones
 right now.

 This makes it difficult for external processes to correctly query Tahoe
 for its version string. I think that "tahoe --version" and the version
 data given to foolscap should use a fixed key (perhaps "tahoe"), and have
 a value which contains the combined appname and release number: {{{tahoe:
 allmydata-tahoe-r5678}}} or {{{tahoe: tahoe-server-r5678}}}.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/652>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid


More information about the tahoe-dev mailing list