Re: How to package a binary provided by python2 and python3

2014-11-04 Thread Barry Warsaw
On Nov 04, 2014, at 10:21 PM, Etienne Millon wrote: >The best practice is indeed to discard the binary in one of the >packages, like your solution 1. However, it is better to use the >python3 version (this is the recommended way now, can't find the >debian-python thread from earlier this year). C

Re: How to package a binary provided by python2 and python3

2014-11-04 Thread Johan Van de Wauw
On Tue, Nov 4, 2014 at 10:21 PM, Etienne Millon wrote: > Hi, > > The best practice is indeed to discard the binary in one of the > packages, like your solution 1. However, it is better to use the > python3 version (this is the recommended way now, can't find the > debian-python thread from earlier

Re: How to package a binary provided by python2 and python3

2014-11-04 Thread Frank Loeffler
Hi, On Tue, Nov 04, 2014 at 09:37:49PM +0100, Johan Van de Wauw wrote: > python3-fiona). My question is what I should do with the binary > '/usr/bin/rio' (or /usr/bin/fiona'): > * include one binary in python-rasterio and discard it from python3-rasterio > * create a seperate package (eg python-r

Re: How to package a binary provided by python2 and python3

2014-11-04 Thread Etienne Millon
Hi, The best practice is indeed to discard the binary in one of the packages, like your solution 1. However, it is better to use the python3 version (this is the recommended way now, can't find the debian-python thread from earlier this year). If most of your users will use only the binary, they