Debian packaging for Python applications and                  libraries           Sheffield Python Group            25 Sep...
Overview●   Making a package    –   The debian/ directory    –   Source packages    –   Binary packages●   PPAs & recipe b...
debian/●   control – metadata for your source package    and binary package(s)●   rules – makefile describing how to build...
Source package●   taxonome_0.12.orig.tar.gz●   taxonome_0.12-1ppa2.debian.tar.gz●   taxonome_0.12-1ppa2.dsc●   taxonome_0....
Binary packagestaxonome_0.12-1ppa1_all.deb●   This is what you install●   Different ways to build:    –   Local build    –...
Demos
PPAs●   Personal Package Archives●   Build and publish your own packages●   Users add PPA to install packages:    –   sudo...
Submitting packages●   ITP: intent to package●   RFS: request for sponsorship●   lintian: automated nitpicking    –   --pe...
The FutureCan we use distutils metadata to make Debianpackages automatically?●   Stdeb (not exactly future)    –   https:/...
More information●   Lots of info on the web, but alternative tools    make it confusing.●   A clear starting point is the ...
Upcoming SlideShare
Loading in...5
×

Debian packaging talk, Pysheff sept 2012

237

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
237
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Debian packaging talk, Pysheff sept 2012

  1. 1. Debian packaging for Python applications and libraries Sheffield Python Group 25 September 2012 Thomas Kluyver
  2. 2. Overview● Making a package – The debian/ directory – Source packages – Binary packages● PPAs & recipe builds● Submitting to Debian or Ubuntu● The future
  3. 3. debian/● control – metadata for your source package and binary package(s)● rules – makefile describing how to build your package● changelog – records each version of the package, defines version number● patches/ – changes applied to the source before building it.● copyright – license info for every file● watch – where to check for newer versions
  4. 4. Source package● taxonome_0.12.orig.tar.gz● taxonome_0.12-1ppa2.debian.tar.gz● taxonome_0.12-1ppa2.dsc● taxonome_0.12-1ppa2_source.changes
  5. 5. Binary packagestaxonome_0.12-1ppa1_all.deb● This is what you install● Different ways to build: – Local build – pbuilder (creates a separate installation) – Build servers (for all published packages)
  6. 6. Demos
  7. 7. PPAs● Personal Package Archives● Build and publish your own packages● Users add PPA to install packages: – sudo apt-add-repository ppa:takluyver/taxonome● Recipe builds: build from VCS every day – Testing, dogfooding
  8. 8. Submitting packages● ITP: intent to package● RFS: request for sponsorship● lintian: automated nitpicking – --pedantic – lintian4py● DFSG: Debian Free Software Guidelines – be very clear about copyright● Ubuntu MyApps system – Applications only, should be simpler – Some teething trouble with reviewing
  9. 9. The FutureCan we use distutils metadata to make Debianpackages automatically?● Stdeb (not exactly future) – https://github.com/astraw/stdeb● pkgme – https://launchpad.net/pkgme● PyPI to Debian repository convertor – https://gitorious.org/pypi2deb
  10. 10. More information● Lots of info on the web, but alternative tools make it confusing.● A clear starting point is the Ubuntu packaging guide:http://developer.ubuntu.com/packaging/html/python-packaging.html● Debian Python Modules Team (DPMT) and Python Apps Packaging Team (PAPT) can help, but aren’t always newcomer-friendly.
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×