Differences between revisions 17 and 18
Revision 17 as of 2011-09-03 16:53:30
Size: 4306
Editor: HenriLeFoll
Comment: merging information from HowToPackageForDebian
Revision 18 as of 2011-09-03 17:06:50
Size: 4321
Editor: HenriLeFoll
Comment: correction : link of Developers Reference
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 * [[http://www.debian.org/doc/debian-policy/|Developers Reference]] -- advanced guide etc.  * [[http://www.debian.org/doc/manuals/developers-reference/|Developers Reference]] -- advanced guide etc.

When you seriously think about packaging as new comer to Debian, please read the official documentation :

Introduction to Debian Packaging

Why programs should be packaged:

  • You want the program to be included in Debian.
  • The packaging system takes care of the old version
  • You want to install programs on severall computers.

First read the excellent Introduction to Debian Packaging.

There is another interesting document on how to package for Debian

There is also an intresting package : packaging-tutorial by Lucas Nussbaum

A very basic introduction of equivs to create :

  • an ?empty package or a ?package with some files

  • a ?dummy package

Please note some Ubuntu resources may be quite useful too.

Building debian packages

To make sure that a debian package meets all build dependencies and is not influenced by anything specific to the user's environment, packages should be built in a chroot environment. Tools like pbuilder can be used for this.

When working on a package, a faster rebuild can be done with 'debuild'. But then, all build-dependencies must be satisfied in the installation where the package is built. All necessary packages can be installA very basic introduction to create an ?empty package or a package with ?just a pdf file ed automatically with apt-get build-dep. A complete example for building the foo package looks like this:

 $ apt-get source foo
 $ cd foo-0.0.1
 $ sudo apt-get build-dep foo
 $ debuild -i -us -uc -b

This is usually enough for you to backport packages.

other informations

Advanced Packaging Procedures

Useful pages

See also:

CategoryPackageManagement CategoryPackaging