Differences between revisions 1 and 42 (spanning 41 versions)
Revision 1 as of 2006-07-22 22:52:27
Size: 33
Editor: EddyPetrisor
Comment: most popular search term should be occupied
Revision 42 as of 2014-01-31 12:06:43
Size: 6268
Editor: BenArmstrong
Comment: Clarify equivs is not a shortcut to learning good packaging practices
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#REDIRECT HowToPackageForDebian #language en
~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: English - [[it/Packaging|Italiano]] - [[sv/Packaging|Svenska]] -~
----

{{{#!wiki debian
When you seriously think about packaging as a newcomer 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/devel-manuals#packaging-tutorial|Debian Packaging Tutorial]] -- slides-based overview of Debian packaging
 * [[http://www.debian.org/doc/debian-policy/|Debian Policy]] -- guiding rules
 * [[http://www.debian.org/doc/manuals/developers-reference/|Developers Reference]] -- advanced guide etc.

}}}

----

<<TableOfContents()>>


== Why Packaging ==

Whether you want
 * to install some programs or data on several computers
 * to have consistent and deterministic versioning
 * the packaging system to take care of updates
 * to help the Debian project. (see [[http://www.debian.org/devel/wnpp/|Work-Needing and Prospective Packages]])

== What is a "package"? ==

There are two kinds of packages: "binary" (.deb) and "source" (.dsc) packages. There are tools (e.g. cpack) that are able to generate "binary" packages but such packaging is ad-hoc (build-system specific) and fragile. Such packages are more likely to fail to operate when the target system diverges from the original environment they were built in.

"source" packages in turn can be built to produce "binary" packages on any other machine and architecture. In a standardized, language and underlying build-system (make vs cmake) agnostic form they provide all the necessary information about build and run-time dependencies and conflicts, a standardized description of copyright and license information, an initial configuration, etc. That is why "binary" packages alone, without the "source" packages originating them, can not be submitted for inclusion into an official Debian distribution.

Therefore ''Packaging'' in the Debian world is primarily concerned with "source" packages. "binary" packages are just a product of such work.

== Introduction to Debian Packaging ==

There are no shorctuts to learning good packaging practices. However, if you have no interest in that and just need to create rapidly a package, use [[DebianPkg:equivs]]:
  * read first [[CreateDummyPackage|how to create an empty package]]
  * then read how to create a [[/Files|package with some files]]

If you prefer to gain real knowledge about Debian packaging:
  * first read the excellent [[IntroDebianPackaging|introduction to Debian Packaging]] to build a package from scratch,
  * you can also look at the [[BuildingTutorial|building tutorial]] to apply changes to an existing package.

Now that you have seen the basics, it is highly recommended that you read some real stuff:
 * [[http://www.debian.org/doc/manuals/maint-guide/index.en.html|the Debian New Maintainers' Guide]] describes the building of a Debian package to ordinary Debian users.
 * [[http://www.debian.org/doc/debian-policy/|the Debian Policy]] includes technical requirements that each package must satisfy.

Then, if you are looking for answers, you can come back here or read:
  * the interesting pdf file included in the package [[DebianPkg:packaging-tutorial|packaging-tutorial]].
  * [[http://www.debian.org/doc/manuals/developers-reference/|The Developers Reference]] provides an overview of the recommended procedures and the available resources for Debian developers.

== Debian Derivatives ==

Please note that some Debian Derivatives resources may be quite useful too.
 * the [[http://developer.ubuntu.com/packaging/html/|Ubuntu Packaging Guide]]

Learn more about the [[DEX|DEX project]]


== Advanced Packaging Procedures ==

=== from Debian Women ===

[[DebianWomen]] organise interesting [[DebianWomen/Projects/Events/TrainingSessions|training sessions]].
Those are about packaging :

 * [[AdvancedBuildingTips|some advanced building tips]]
 * [[Courses2005/BuildingWithoutHelper|How to make a Debian package without using a helper]]
 * [[/HackingDependencies|hacking dependencies]]

=== See also ===
 * [[UsingQuilt]]
 * [[PackagingFAQ]]
 * [[Renaming_a_Package]]
 * PackageTransition
 * [[Adding and removing diversions]]
 * BzrBuildpackage/DesignIdeas
 * PackagingWithDarcs
 * PackagingWithGit
 * PbuilderTricks
 * [[PkgSplit|How to split a package into smaller packages]]
 * [[Repackage_srcrpm]] - creating a proper Debian source package while referencing the src.rpm package
 * [[RPM]] - Converting a .RPM into .DEB with alien - generally leads to bad results
 * DebugPackage
 * [[PackageArchitectureAlmostAny|Creating package without some particular architectures]] - for easy porting
 * [[Python/Packaging]]
 * ConfigPackages
 * EditingBinaryPackageMetadata

=== Useful pages ===
 * SoftwarePackaging
 * SponsorChecklist
 * SecurePbuilder
 * [[HowToPackageForDebian|how to package for Debian]]
 * [[Package]]

== other informations ==

=== External useful links ===
 * http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Debian-Binary-Package-Building-HOWTO.html
 * http://qref.sourceforge.net/Debian/reference/ch-package.en.html
 * http://www.debian.org/doc/manuals/apt-howto/ and package apt-howto
 * http://www.debian.org/devel/wnpp/prospective : requested packages, and packages being worked on.
 * [[http://people.connexer.com/~roberto/howtos/debcustomize|Debian Package Customization HOWTO]]
 

=== See also: ===
 * http://www-128.ibm.com/developerworks/linux/library/l-debpkg.html : creating debian packages - high-level description of debian packaging .
 * WikiPedia:List_of_open-source_software_packages
 * [[http://www.debian-administration.org/articles/336]] Rolling your own debian packages.
 * [[http://vcs-pkg.org/|VCSPackaging]]
 * Autobuilding non-free packages: http://article.gmane.org/gmane.linux.debian.devel.announce/997

 * AutomakeTransition
 * PackageConfigUpgrade : propose a new way to smoothly handle configuration upgrades during package upgrades
 * DataPackages
----
CategoryPackageManagement CategoryPackaging
----

Translation(s): English - Italiano - Svenska


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


Why Packaging

Whether you want

  • to install some programs or data on several computers
  • to have consistent and deterministic versioning
  • the packaging system to take care of updates
  • to help the Debian project. (see Work-Needing and Prospective Packages)

What is a "package"?

There are two kinds of packages: "binary" (.deb) and "source" (.dsc) packages. There are tools (e.g. cpack) that are able to generate "binary" packages but such packaging is ad-hoc (build-system specific) and fragile. Such packages are more likely to fail to operate when the target system diverges from the original environment they were built in.

"source" packages in turn can be built to produce "binary" packages on any other machine and architecture. In a standardized, language and underlying build-system (make vs cmake) agnostic form they provide all the necessary information about build and run-time dependencies and conflicts, a standardized description of copyright and license information, an initial configuration, etc. That is why "binary" packages alone, without the "source" packages originating them, can not be submitted for inclusion into an official Debian distribution.

Therefore Packaging in the Debian world is primarily concerned with "source" packages. "binary" packages are just a product of such work.

Introduction to Debian Packaging

There are no shorctuts to learning good packaging practices. However, if you have no interest in that and just need to create rapidly a package, use equivs:

  • read first ?how to create an empty package

  • then read how to create a ?package with some files

If you prefer to gain real knowledge about Debian packaging:

Now that you have seen the basics, it is highly recommended that you read some real stuff:

Then, if you are looking for answers, you can come back here or read:

Debian Derivatives

Please note that some Debian Derivatives resources may be quite useful too.

Learn more about the DEX project

Advanced Packaging Procedures

from Debian Women

DebianWomen organise interesting training sessions. Those are about packaging :

See also

Useful pages

other informations

See also:


CategoryPackageManagement CategoryPackaging