[tahoe-dev] [tahoe-lafs] #745: Debian package: Missing dependency on Debian/etch

[tahoe-lafs]

#745: Debian package: Missing dependency on Debian/etch
------------------------------+---------------------------------------------
 Reporter:  [4-tea-2]         |           Owner:  warner
     Type:  defect            |          Status:  new   
 Priority:  major             |       Milestone:  1.5.0 
Component:  packaging         |         Version:  1.4.1 
 Keywords:  debian,packaging  |   Launchpad_bug:        
------------------------------+---------------------------------------------

Comment(by warner):

 Sigh. So, building separate .debs for py2.4/py2.5/py2.6 is painful (nobody
 does it anymore, now that debian-python-policy generates .pycs at install
 time). And I don't believe the .deb control-file "Depends:" format isn't
 rich enough to express (py>=2.5 or pysqlite).

 On the other hand, the "standard" version of python is well-known per-
 platform (it's 2.4 in the older ones, 2.5 in the newer ones, and I guess
 Ubuntu Karmic will probably have 2.6). So we could say that when we build
 a .deb on a platform with /usr/bin/python=2.4, we declare the dependency
 upon pysqlite, and when we build it on a py2.5-using platform, we don't.

 To implement this, we should update the misc/*/debian/control files to
 declare the pysqlite dependency on the older platforms, and leave the
 newer ones alone (not declaring it).

 This also means that we should probably stop using the feisty rules for
 all platforms.. we at least need to identify the release for which python
 switched to 2.5 and use a newer set of rules for the 2.5-using set.

 I'll try to look at this today, but I'm not sure I'll get the time.

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