Sources
Help build the largest human-edited directory on the web.
Submit a site - Become an editor
Wikipedia. Licensed under the GNU Free Documentation License.
Are you an expert in this subject? Join the discussion and share your knowledge at Wikipedia.org.
Dpkg
From Wikipedia, the free encyclopedia
- The correct title of this article is dpkg. The initial letter is shown capitalized due to technical restrictions.
| dpkg | |
| Developer: | the dpkg team |
|---|---|
| Use: | Package management system |
| Website: | |
dpkg (short for Debian PacKaGe) is the base of the Debian package management system. It was created by Ian Jackson in 1993. dpkg is similar to RPM, as it is used to install, remove, and provide information about .deb packages.
dpkg itself is a low level tool; higher level tools, such as APT, are used to fetch packages from remote locations or deal with complex package relations.
The Debian package "dpkg" provides the dpkg program, as well as several others necessary for run-time functioning of the packaging system, including dpkg-statoverride, dpkg-divert and update-alternatives. It also includes the programs such as start-stop-daemon and install-info, and the latter is kept mostly due to backwards compatibility (it is developed and distributed separately nowadays). The Debian package "dpkg-dev" includes the numerous build tools described below.
ipkg is a dpkg-inspired package management system for storage-constrained Linux installations.
Contents |
debs are usually built by calling dpkg-buildpackage. dpkg-buildpackage reads several files to figure out how to build the package. These files are located in the debian subdirectory of a source tree.
There are four required files. The copyright file contains license terms. The control file contains the package name, description, and dependencies. The rules file is a Makefile that has rules for building a debian package. Programs from the debhelper program suite are often called in the rules file. In addition, some packages include Makefile snippets from CDBS, greatly simplifying the rules file. Finally there is the changelog file, which, predictably, contains the changelog. Most packages also include other files for doing various things.
Once a Debian package is built, it can be checked for common problems using the lintian tool.
Debian has a series of tools that have to be called to construct a package. They are the following:
- dpkg-source packs and unpacks the source files of a Debian package.
- dpkg-deb packs and unpacks binary packages
- dpkg-gencontrol reads the information from an unpacked Debian tree source and generates a binary package control package, creating an entry for this in Debian/files.
- dpkg-shlibdeps calculates the dependencies of runs with respect to libraries.
- dpkg-genchanges reads the information from an unpacked Debian tree source that once constructed creates a control file (.changes).
- dpkg-buildpackage is a control script that can be used to construct the package automatically.
- dpkg-distaddfile adds a file input to debian/files.
- dpkg-parsechangelog reads the changes file (changelog) of an unpacked Debian tree source and creates a conveniently prepared output with the information for those changes.
