[Ben Finney, 2015-02-23]
> I am working to package a collection of related Python distributions,
> that are all distributed as a single source distribution
> <URL:https://pypi.python.org/pypi/devpi/>.
>
> The source distribution contains a collection of sub-distributions that
> also get uploaded to PyPI. Each one has its own ‘setup.py’ in a
> sub-directory.
>
> That differs from the default expectations of Debhelper and Pybuild (it
> does not build a single binary distribution from a single top-level
> ‘setup.py’).
>
> What is the correct way to convince Debhelper, Pybuild, dh_python{2,3},
> etc. to work with this source package and build the right binary
> packages?
hints: (I didn't test it)
* name your tarballs like this (dpkg-source will unpack them to the
right dir later)
devpi_2.1.0.orig.tar.gz
devpi_2.1.0.orig-client.tar.gz
devpi_2.1.0.orig-server.tar.gz
devpi_2.1.0.orig-web.tar.gz
* in debian/rules use:
export PYBUILD_NAME=devpi
%:
dh $@ --with python2,python3 --buildsystem=pybuild --sourcedirectory=server
dh $@ --with python2,python3 --buildsystem=pybuild --sourcedirectory=client
dh $@ --with python2,python3 --buildsystem=pybuild --sourcedirectory=web
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Attachment:
signature.asc
Description: Digital signature