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 .
This commit is contained in:
Brian Warner 2007-09-26 17:52:30 -07:00
parent 20238f0105
commit d41f0f9492

View File

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