On 30/08/14 10:50, Cornelius Kölbel wrote:
> But now my originial program package is empty and does not contain the
> python code.
> It looks like only the .install scripts are run, but obviously python
> setup.py install is not run anymore - so I guess something does not work
> right with the simple rules file anymore...
You now need a .install file for each binary package, including your
original one.
If there is only one binary package in debian/control (e.g.
python-privacyidea, like in your original situation) then debhelper
defaults to telling setup.py to install into debian/python-privacyidea/
which ends up as the python-privacyidea package.
If there is more than one binary package in debian/control, debhelper
defaults to telling setup.py to install into debian/tmp/ (which does not
automatically install to any binary packages), then you have to arrange
for the files in debian/tmp/ to be copied into
debian/python-privacyidea/ and debian/python-privacyidea-data/ (or
whatever your other package is called). Writing debian/*.install is the
usual way to achieve that.
S
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5401a51c....@debian.org
