From: Brian Warner <warner@allmydata.com>
Date: Thu, 27 Sep 2007 00:52:30 +0000 (-0700)
Subject: debian/feisty: use our original bin/allmydata-tahoe instead of setuptools's
X-Git-Tag: allmydata-tahoe-0.6.1~71
X-Git-Url: https://git.rkrishnan.org/%5B/%5D%20/frontends/somewhere?a=commitdiff_plain;h=d41f0f949201d1a5c289f59404596d524991aab3;p=tahoe-lafs%2Ftahoe-lafs.git

debian/feisty: use our original bin/allmydata-tahoe instead of setuptools's
because the setuptools "entry points" form asserts that there are
setuptools-visible packages like nevow/zope.interface (i.e. they have .egg-info
metadata). Until very recently, most debian systems did not install this
metadata. Instead, we rely upon the usual debian dependency checking as
expressed in debian/control .
---

diff --git a/misc/feisty/debian/rules b/misc/feisty/debian/rules
index 5abfddcb..3d669dae 100644
--- a/misc/feisty/debian/rules
+++ b/misc/feisty/debian/rules
@@ -9,9 +9,21 @@ include /usr/share/cdbs/1/class/python-distutils.mk
 
 STAGING_DIR=$(CURDIR)/debian/allmydata-tahoe
 
+# we overwrite the setuptools-generated /usr/bin/allmydata-tahoe with our
+# package's original version, because the setuptools form (using "entry
+# points") insists upon .egg-info -visible forms of dependent packages to be
+# installed. For a debian package, we rely upon the dependencies that are
+# declared in debian/control .
+#
+# One disadvantage to this approach is that the #! line will not get updated
+# to match the version of python that we're using for this build. Instead, it
+# will retain the original '#!/usr/bin/env python', which has the potential
+# to surprise people.
+
 install/allmydata-tahoe::
 	mkdir -pm755 $(STAGING_DIR)
 	python setup.py install --root=$(STAGING_DIR)
+	cp bin/allmydata-tahoe $(STAGING_DIR)/usr/bin/
 
 	dh_pycentral