Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #7861 > unrolled thread

Any suggested procedure if upstream does not provide any build helper like setup.py

Back to article view | Back to linux.debian.maint.python

Contents

  Any suggested procedure if upstream does not provide any build  helper like setup.py Andreas Tille <andreas@an3as.eu> - 2015-11-20 16:20 +0100
    Re: Any suggested procedure if upstream does not provide any build  helper like setup.py Piotr Ożarowski <piotr@debian.org> - 2015-11-20 16:30 +0100
      Re: Any suggested procedure if upstream does not provide any build  helper like setup.py Mrudula Chougule <chougulemrudula@gmail.com> - 2015-11-20 16:50 +0100
        Re: rtai Brian May <bam@debian.org> - 2015-11-21 01:20 +0100
    Re: Any suggested procedure if upstream does not provide any build helper like setup.py Brian May <bam@debian.org> - 2015-11-21 01:10 +0100
    Re: Any suggested procedure if upstream does not provide any build  helper like setup.py Thomas Goirand <zigo@debian.org> - 2015-11-21 19:10 +0100

#7861 — 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/<subdirs>.
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

[toc] | [next] | [standalone]

#7862

[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/<subdirs>.
> 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

[toc] | [prev] | [next] | [standalone]

#7863

[Multipart message — attachments visible in raw view] — view raw

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 <piotr@debian.org> 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/<subdirs>.
> > 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
>
>

[toc] | [prev] | [next] | [standalone]

#7865 — Re: rtai

Mrudula Chougule <chougulemrudula@gmail.com> 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 <bam@debian.org>

[toc] | [prev] | [next] | [standalone]

#7864 — Re: Any suggested procedure if upstream does not provide any build helper like setup.py

Andreas Tille <andreas@an3as.eu> 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/<subdirs>.
> 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 <bam@debian.org>

[toc] | [prev] | [next] | [standalone]

#7866

On 11/20/2015 04:12 PM, Andreas Tille wrote:
> 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/<subdirs>.
> There is no makefile of setup.py.  Is there any suggested procedure how
> to build a package from this?
> 
> Kind regards
> 
>        Andreas.

If the project is hosted on something like github, I'd suggest a
setup.py to upstream. And in fact, I'd suggest one using PBR, which is a
wonderful tool, if you didn't know it. Basically, everything lives in
the setup.cfg in a declarative way, and there's no code to write, PBR
does everything for you. There's more than 100 examples of use (and
abuse) of PBR in the OpenStack world (github.com/openstack).

Cheers,

Thomas Goirand (zigo)

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web