ewiger / gc3pie

Automatically exported from code.google.com/p/gc3pie
0 stars 0 forks source link

Provide Debian/Ubuntu package #100

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Create a `debian/control` file for building a Debian/Ubuntu package.

Register gc3pie on Launchpad so we can have a PPA repository for building the 
gc3pie packages on Ubuntu.

Original issue reported on code.google.com by riccardo.murri@gmail.com on 12 Jan 2011 at 11:07

GoogleCodeExporter commented 9 years ago
Please use `yada`[1] or `pkgme`[2] to create the package.

(We already use YADA for AppPot [3] with good results.)

[1]: http://yada.alioth.debian.org/
[2]: http://jameswestby.net/weblog/tech/23-pkgme-handles-packaging-for-you.html
[3]: http://apppot.googlecode.com/

Original comment by riccardo.murri@gmail.com on 6 Feb 2012 at 10:59

GoogleCodeExporter commented 9 years ago
I guess the main problem in packaging GC3Pie is how to encode the dependency on 
other Python packages; we currently depend on ARClib, Paramiko, PyCLI, and 
Lockfile, and will depend on more in the future.

ARClib and Paramiko are already packaged for Debian/Ubuntu and available from 
the main or other well-known repositories.

PyCLI and Lockfile are *not* already packaged as far as I can tell.  I can see 
only two ways of attacking this problem:

a. Either package PyCLI and Lockfile, and contribute the packaging upstream. 
(But we host a copy of the package in our repositories until it gets accepted.)

b. Or we include a local copy of the package in the `gc3libs.compat` namespace.

I guess with "a." is the "right" thing to do and best for all in the long run, 
but "b." might be faster and easier.

Original comment by riccardo.murri@gmail.com on 6 Feb 2012 at 11:05

GoogleCodeExporter commented 9 years ago

Original comment by riccardo.murri@gmail.com on 6 Feb 2012 at 11:06

GoogleCodeExporter commented 9 years ago
I'm incline to second `a.', even if I am supposed to do the packaging :)

There is a "c." option maybe: replace PyCLI with something more widely 
supported, like twisted.python.usage. I don't know about lockfile though.

Original comment by arcimbo...@gmail.com on 6 Feb 2012 at 12:15

GoogleCodeExporter commented 9 years ago
| Comment #4 on issue 100 by arcimboldo: Provide Debian/Ubuntu package
| http://code.google.com/p/gc3pie/issues/detail?id=100
|
| There is a "c." option maybe: replace PyCLI with something more widely
| supported, like twisted.python.usage.
|

Feel free to suggest and code a replacement for PyCLI, but
`twisted.python.usage` is not: `twisted.python.usage` is a
replacement for stdlib's `getopt` or `argparse`, whereas PyCLI is a
small set of skeleton classes that implement the boilerplate that goes
into every command-line script.  (Much like GC3Pie aims to do for
high-throughput scripts.)

Original comment by riccardo.murri@gmail.com on 6 Feb 2012 at 1:36

GoogleCodeExporter commented 9 years ago
Comment #3 on Issue 101 also applies here: consider 
https://github.com/ytoolshed/multipkg as an alternative to `pkgme`.

Original comment by riccardo.murri@gmail.com on 16 Mar 2012 at 9:48

GoogleCodeExporter commented 9 years ago
I'm trying python-stdeb. "It just works": you simply download the tar.gz for 
each dependency, run py2dsc and then dpkg-buildpackage. (It should be able to 
download using pip by itself, but on my squeeze didn't work)

For lockfile, for instance:

   wget http://pylockfile.googlecode.com/files/lockfile-0.9.1.tar.gz
   py2dsc lockfile-0.9.1.tar.gz 
   cd deb_dist/lockfile-0.9.1/
   dpkg-buildpackage -rfakeroot -uc -us

For gc3pie, instead, you have to enter the source repository and then run:

    python setup.py --command-packages=stdeb.command bdist_deb
    cd deb_dist/gc3pie-1.1~dev/
    dpkg-buildpackage -rfakeroot -uc -us

of course you need to have python-stdeb installed.

Original comment by arcimbo...@gmail.com on 11 Apr 2012 at 12:52

GoogleCodeExporter commented 9 years ago
+ dependencies are automatically converted. For instance, if in setup.py you 
have 

      'install-requires':'lockfile' 

  it will be converted in

      Depends: python-lockfile

  into the debian/control file

- with paramiko, for instance, it will not work, since the python package name 
is `pycrypto` while the debian package is `python-crypto`. However, it is 
possible to customize the package generation using both command line options or 
a configuration file.

Original comment by arcimbo...@gmail.com on 11 Apr 2012 at 1:31

GoogleCodeExporter commented 9 years ago

Original comment by riccardo.murri@gmail.com on 8 Aug 2012 at 7:06

GoogleCodeExporter commented 9 years ago

Original comment by riccardo.murri@gmail.com on 17 Aug 2012 at 11:46

GoogleCodeExporter commented 9 years ago
It could be interesting to use SuSE's "Open Build Service" for this:

http://openbuildservice.org/about/

It can also build Debian/Ubuntu packages.

Original comment by riccardo.murri@gmail.com on 5 Aug 2014 at 12:14