[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1159: stop using .tac files: make it possible to change appname, Python package-directory name, perhaps other names

[Tahoe-LAFS]

#1159: stop using .tac files: make it possible to change appname, Python package-
directory name, perhaps other names
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  warner
  davidsarah             |     Status:  new
         Type:  defect   |  Milestone:  1.11.0
     Priority:  major    |    Version:  1.8β
    Component:  code-    |   Keywords:  test-needed backward-compatibility
  nodeadmin              |  forward-compatibility appname tac needs-spawn
   Resolution:           |  packaging setuptools review-needed
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by warner):

 I've rebased the branch (and fixed one test which was failing.. not sure
 what exactly was happening there, the fix was to revert a test change that
 I made to allow the original patch to pass). The new branch is here:

 https://github.com/warner/tahoe-lafs/tree/1159-notac-2

 I think we should land this, and then close #1539 because this branch
 supercedes that one.

 Note that this patch doesn't completely close #1159: it stops using the
 *contents* of the .tac files, but still relies upon their presence, in
 particular their filename: if "client" is a substring of the filename of
 the first .tac file found in the node's basedir, then we instantiate a
 `Client`, if "introducer" is in the string, we instantiate an
 `IntroducerNode`, etc.

 We'll want another patch, after 1.11, to move this indicator into
 tahoe.cfg (and look for a .tac filename as a backwards-compatibility
 tool).

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1159#comment:50>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage