Re: multiple deb packages from python program.

2014-08-30 Thread Barry Warsaw
On Aug 30, 2014, at 09:00 PM, Piotr Ożarowski wrote: >export PYBUILD_NAME=foo Best thing *ever*. :) -Barry -- 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/2014083

Re: multiple deb packages from python program.

2014-08-30 Thread Piotr Ożarowski
[Scott Kitterman, 2014-08-30] > Interesting. I've always had to add them. export PYBUILD_NAME=foo does the trick -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2

Re: multiple deb packages from python program.

2014-08-30 Thread Scott Kitterman
On August 30, 2014 1:06:41 PM EDT, Barry Warsaw wrote: >On Aug 30, 2014, at 12:57 PM, Scott Kitterman wrote: > >>I don't think that's the case for multiple binary packages. > >Hmm. An example is enum34, which has python-enum34, python3-enum34, >and >python-enum34-doc binary packages. I don't hav

Re: multiple deb packages from python program.

2014-08-30 Thread Barry Warsaw
On Aug 30, 2014, at 12:57 PM, Scott Kitterman wrote: >I don't think that's the case for multiple binary packages. Hmm. An example is enum34, which has python-enum34, python3-enum34, and python-enum34-doc binary packages. I don't have any d/*.install files and everything gets built correctly. h

Re: multiple deb packages from python program.

2014-08-30 Thread Scott Kitterman
On Saturday, August 30, 2014 09:44:30 Barry Warsaw wrote: > On Aug 30, 2014, at 11:19 AM, Simon McVittie wrote: > >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 ar

Re: multiple deb packages from python program.

2014-08-30 Thread Barry Warsaw
On Aug 30, 2014, at 11:19 AM, Simon McVittie wrote: >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

Re: multiple deb packages from python program.

2014-08-30 Thread Simon McVittie
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 simp