Differences between revisions 16 and 17
Revision 16 as of 2011-08-31 19:12:51
Size: 3289
Editor: HenriLeFoll
Comment: add link to equivs
Revision 17 as of 2011-09-03 16:53:30
Size: 4306
Editor: HenriLeFoll
Comment: merging information from HowToPackageForDebian
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
{{{#!wiki debian
When you seriously think about packaging as new comer to Debian, please read the official documentation :

 * [[http://www.debian.org/doc/manuals/maint-guide/index.en.html|the Debian New Maintainers' Guide]] -- tutorial for simple package
 * [[http://www.debian.org/doc/debian-policy/|Debian Policy]] -- guiding rules
 * [[http://www.debian.org/doc/debian-policy/|Developers Reference]] -- advanced guide etc.

}}}

----
Line 6: Line 17:
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.

##, so if a file is moved in the source, uninstall still works properly (unlike when you use make uninstall with the new Makefile)
Line 16: Line 34:

== Debian Packaging ==

When you seriously think about packaging as new comer to Debian, please consider to read:

 * [[http://www.debian.org/doc/manuals/maint-guide/index.en.html|the Debian New Maintainers' Guide]] -- tutorial for simple package
 * [[http://www.debian.org/doc/debian-policy/|Debian Policy]] -- guiding rules
 * [[http://www.debian.org/doc/debian-policy/|Developers Reference]] -- advanced guide etc.
Line 27: Line 36:

Line 47: Line 54:
== See also: == == other informations ==

=== Advanced Packaging Procedures ===
 * [[Renaming_a_Package]]
 * [[Adding and removing diversions]]
 * BzrBuildpackage/DesignIdeas
 * PackagingWithDarcs
 * PackagingWithGit
 * PbuilderTricks
 * [[PkgSplit|How to split a package into smaller packages]]
 * [[RPM]] - Converting a .RPM into .DEB - generally leads to bad results
 * DebugPackage
 * [[PackageArchitectureAlmostAny|Creating package without some particular architectures]] - for easy porting

=== External useful links ===
 * http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Debian-Binary-Package-Building-HOWTO.html
 * https://wiki.ubuntu.com/MOTU/Packages/Packaging/Tips
 * http://qref.sourceforge.net/Debian/reference/ch-package.en.html
 * http://www.debian.org/doc/manuals/apt-howto/ and package apt-howto

=== Useful pages ===
 * SoftwarePackaging

=== See also: ===
Line 57: Line 87:
 * DebugPackage
Line 61: Line 90:
 * PackagingWithDarcs
 * PackagingWithGit
 * [[PkgSplit|Making Multiple Packages From A Single Source Tarball]]
 * [[Renaming_a_Package]]
Line 70: Line 96:
 * [[RPM|rpm]] - Tool for extracting from RPM source tarballs

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