From d41f0f949201d1a5c289f59404596d524991aab3 Mon Sep 17 00:00:00 2001
From: Brian Warner <warner@allmydata.com>
Date: Wed, 26 Sep 2007 17:52:30 -0700
Subject: [PATCH] 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 .

---
 misc/feisty/debian/rules | 12 ++++++++++++
 1 file changed, 12 insertions(+)

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
 
-- 
2.45.2