[tahoe-dev] [tahoe-lafs] #1220: build/install should be able to refrain from getting dependencies

[tahoe-lafs]

#1220: build/install should be able to refrain from getting dependencies
-----------------------+----------------------------------------------------
 Reporter:  gdt        |           Owner:  somebody 
     Type:  defect     |          Status:  new      
 Priority:  major      |       Milestone:  undecided
Component:  packaging  |         Version:  1.8.0    
 Keywords:             |   Launchpad Bug:           
-----------------------+----------------------------------------------------
 In a managed package system, each program's dependencies are expressed in
 control files and provided before the package builds.  If the package has
 more dependencies than expresssed, the right behavior is failure so that
 this can be fixed, and it is unhelpful to download/install code either
 from included eggs or especially from the net.

 There are two parts to this problem.  One is downloading and installing
 things like py-cryptopp.  The other is that tahoe seems to have to need
 modified versions of standard tools and has included eggs.  This kind of
 divergence should be resolved.

 I realize that this complaint is perhaps directed at setuptools, but
 tahoe-lafs inherits responsibility.

 A reasonable solution would be to have a switch that packaging systems can
 add.

 I put this on packaging even though the bug is in tahoe-lafs, not in any
 packaging of it.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1220>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage