[tahoe-lafs-trac-stream] [tahoe-lafs] #1479: Makefile/setup.py cleanups

[tahoe-lafs]

#1479: Makefile/setup.py cleanups
------------------------+--------------------------
     Reporter:  warner  |      Owner:  somebody
         Type:  task    |     Status:  closed
     Priority:  major   |  Milestone:  1.9.0
    Component:  code    |    Version:  1.8.2
   Resolution:  fixed   |   Keywords:  needs-review
Launchpad Bug:          |
------------------------+--------------------------

Comment (by davidsarah):

 Replying to [comment:1 warner]:
 > Replacing $(RUNPP) with something in our {{{bin/tahoe}}} loses the
 > ability to get a repl running without actually importing the tahoe code
 > (at least allmydata.scripts and that infernal {{{__init__.py}}}).

 Well, this guarantees that we do the same checks on package versions
 (which are necessary to detect the situation in #1258) when starting a
 repl as we do when running the CLI, and for the unit tests (#1296). The
 path setup code is so flaky that I really prefer that there is only one
 kind of flakiness rather than several.

 > Relying more heavily upon the gross 'darcsver'-prefixing in setup.cfg is
 > bad, since I want to get rid of setuptools and this reliance makes that
 > more difficult, but I don't have the energy to fight for the Makefile
 > any more.

 When we get rid of the prefixing in setup.cfg, it'll automatically be got
 rid of for the Makefile targets as well.

 > So I'm +1 on this as long as we really try to make bin/tahoe and
 > {{{__init__.py}}} and our {{{setup.py}}} simpler in the near future.

 Just try and stop me! ;-)

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1479#comment:3>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage