transfert package to intro
add link to Diagrams
|Deletions are marked like this.||Additions are marked like this.|
|Line 50:||Line 50:|
|* [[http://pkg-haskell.alioth.debian.org/haskell-policy/|Haskell]] - libraries (outdated, updating is listed as TODO item on [[Haskell]])||* [[Teams/DebianHaskellGroup|Haskell]] - libraries|
|Line 53:||Line 53:|
|* [[http://pkg-lua.alioth.debian.org/policy.html|Lua]] - modules||* [[https://salsa.debian.org/lua-team|Lua]] - modules|
|Line 56:||Line 56:|
|* [[http://pkg-ocaml-maint.alioth.debian.org/ocaml_packaging_policy.html/index.html|OCaml]] - libraries||* [[Teams/OCamlTaskForce|OCaml]] - libraries|
|Line 102:||Line 102:|
|* [[Diagrams]] - packaging related diagrams and sketches|
This portal talk about information relevant to developers wishing to package software for Debian..
Debian packages are maintained by a community of Debian Developers and volunteers.
If you were looking for information on installing and removing packages from your Debian system,
see the package management pages instead.
If you're just starting out with Debian packaging, please read the official documentation first:
Introduction to Debian Packaging
To get a good grounding in Debian packaging:
first read the excellent introduction to Debian Packaging to build a package from scratch,
you can also look at the building tutorial to apply changes to an existing package.
if you are new to debian, then setting up debian unstable system can help you setup a development environment.
Now that you have seen the basics, it is highly recommended that you read some real stuff:
the Debian New Maintainers' Guide describes the building of a Debian package to ordinary Debian users.
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 packaging-tutorial.
The Developers Reference provides an overview of the recommended procedures and the available resources for Debian developers.
What not to do:
There are no shortcuts to learning good packaging practices. Avoid equivs which is only useful for building trivial metapackages and does not teach you anything about packaging.
Types / Formats
AndroidTools - android tools
Fonts - packages
Go - libraries and applications
Haskell - libraries
Java - libraries and applications
Lua - modules
Mono - libraries and applications
Mozilla Extensions - XUL extensions
OCaml - libraries
Python - modules and applications
Ruby - modules and applications
RPM - repackaging RPM packages as .deb packages
Quilt - patch management
Darcs - version control
Git - version control
sbuild - clean build tool
Pbuilder - clean build tool
Secure Pbuilder - builder tool
build scripts used by ruby team - helps testing reverse dependencies easily
Mentors sponsors/mentors for packages in specific areas of Debian
?Adding and removing diversions
?How to split a package into smaller packages
Repackage_srcrpm - creating a proper Debian source package while referencing the src.rpm package
Creating package without some particular architectures - for easy porting
DpkgConffileHandling - Gracefully Handling conffiles
DEX - improving Debian and its derivatives through cross-community teamwork
Repacking - Collecting information about repacking
PackageConfigUpgrade : propose a new way to smoothly handle configuration upgrades during package upgrades
Diagrams - packaging related diagrams and sketches
From Debian Women
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.
What's in a debian/ directory - detailed worked example
http://www-128.ibm.com/developerworks/linux/library/l-debpkg.html : creating debian packages - high-level description of debian packaging .
http://www.debian-administration.org/articles/336 Rolling your own debian packages.
Autobuilding non-free packages: http://article.gmane.org/gmane.linux.debian.devel.announce/997