Any suggested procedure if upstream does not provide any build helper like setup.py
Hi, I'd like to package something that has a source.py in the main directory of the download tarball and a bunch of Python files ins src/. There is no makefile of setup.py. Is there any suggested procedure how to build a package from this? Kind regards Andreas. -- http://fam-tille.de
Re: Any suggested procedure if upstream does not provide any build helper like setup.py
[Andreas Tille, 2015-11-20] > I'd like to package something that has a source.py in the main directory > of the download tarball and a bunch of Python files ins src/. > There is no makefile of setup.py. Is there any suggested procedure how > to build a package from this? I'd simply list them in debian/foo.install files (with proper destination directory) -- 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
Re: Any suggested procedure if upstream does not provide any build helper like setup.py
Hi, I would like to build debian for source code of rtai with python-3 dependencies. Could you please explain brief on modification of building rules for python-3. Appreciate your suggestions. I need those badly!! Thanks On Fri, Nov 20, 2015 at 9:27 AM, Piotr Ożarowski wrote: > [Andreas Tille, 2015-11-20] > > I'd like to package something that has a source.py in the main directory > > of the download tarball and a bunch of Python files ins src/. > > There is no makefile of setup.py. Is there any suggested procedure how > > to build a package from this? > > I'd simply list them in debian/foo.install files (with proper > destination directory) > -- > 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 > >
Re: Any suggested procedure if upstream does not provide any build helper like setup.py
Andreas Tille writes: > I'd like to package something that has a source.py in the main directory > of the download tarball and a bunch of Python files ins src/. > There is no makefile of setup.py. Is there any suggested procedure how > to build a package from this? You could accidentally take over the package upstream, fix it up, upload to PyPI, then do the Debian packaging. I am actually doing this insane process at the moment with sshuttle. After the previous upstream lost interest. So far nobody has complained. Nobody has commented in fact. What could possible go wong? If I break homebrew (MacOSX packages), that might upset people however. Might try and see if I can test formulas using linuxbrew first. There actually good reasons for upstream to do this, e.g. I think a proper setup.py is a requirement to get packages into PyPI. -- Brian May
Re: rtai
Mrudula Chougule writes: > I would like to build debian for source code of rtai with python-3 > dependencies. Could you please explain brief on modification of building > rules for python-3. > > Appreciate your suggestions. I need those badly!! I changed the subject, not sure what this had to do with missing setup.py files. If the upsteam code is not already Python3 compatible, first you will need to be confident upstream will be willing to incorporate your changes. Or you need to be comfortable with forking the project and maintaining it yourself. Otherwise you risk doing a lot of work, and having it not go anywhere. Good automatic tests really help with catching the problems too. If there are no automatic tests, be prepared to miss breakages in the code. I assume you mean this project? https://www.rtai.org/ - if so, looks like they are still using CVS... -- Brian May
