[tahoe-lafs-trac-stream] [tahoe-lafs] #1693: flogtool doesn't get automatically provided

[tahoe-lafs]

#1693: flogtool doesn't get automatically provided
---------------------------+---------------------------------------------
     Reporter:  zooko      |      Owner:  zooko
         Type:  defect     |     Status:  new
     Priority:  normal     |  Milestone:  1.10.0
    Component:  packaging  |    Version:  1.9.1
   Resolution:             |   Keywords:  doc packaging usability logging
Launchpad Bug:             |
---------------------------+---------------------------------------------
Changes (by warner):

 * keywords:  doc packaging usability logging review-needed => doc packaging
     usability logging


Comment:

 The patch looks good, and I'm landing it. One quibble about the docs it's
 modifying, though: the specific PYTHONPATH issue is when Foolscap was only
 installed as part of Tahoe, and therefore bin/foolscap wasn't available
 from outside the tahoe tree's copy. The exception cited in the original
 report looks like it was a pkg_resources problem (probably because
 pkg_resources was only installed as part of Tahoe). My quibble is that I
 want to avoid giving the impression that tahoe itself has to be on
 PYTHONPATH to use 'flogtool' against a Tahoe process. That's very much not
 the case: nothing in the logfiles or event stream requires the original
 application's source code to display. (there have been bugs in tahoe
 and/or foolscap which have made it seem like this must be necessary, but
 really, flogfiles are app-independent).

 I may update the docs at some point to reflect this better.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1693#comment:6>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage