Install dpkg with Homebrew

Project links

• Homepage

Commands and aliases

• dpkg
• dpkg-architecture
• dpkg-buildapi
• dpkg-buildflags
• dpkg-buildpackage
• dpkg-buildtree
• dpkg-checkbuilddeps
• dpkg-deb
• dpkg-distaddfile
• dpkg-divert
• dpkg-genbuildinfo
• dpkg-genchanges
• dpkg-gencontrol
• dpkg-gensymbols
• dpkg-maintscript-helper
• dpkg-mergechangelogs
• dpkg-name
• dpkg-parsechangelog
• dpkg-query
• dpkg-realpath
• dpkg-scanpackages
• dpkg-scansources
• dpkg-shlibdeps
• dpkg-source
• dpkg-split
• dpkg-statoverride
• dpkg-trigger
• dpkg-vendor
• update-alternatives

Project history

dpkg belongs to Debian's earliest packaging culture. Debian's official project history says Debian was founded by Ian Murdock on 16 August 1993, at a time when the idea of a Linux distribution was still new, and that Debian became micro packaged with detailed dependency information to keep systems consistent across upgrades.

The dpkg team page describes the team as responsible for dpkg and related tools used for low-level source and binary package management. The dpkg homepage identifies the project as the Debian Package Manager and points to released tarballs, historic tarballs, the git repository, specifications, API documentation, bug tracking, mailing lists, and downstream distributions.

The dpkg project's own history file records several source-control eras: CVS for dpkg 1.4.1 through 1.10.24, Arch maintenance beginning in December 2004, Subversion from January 2006 through July 2007, and Git beginning 25 July 2007. That VCS trail is part of dpkg's institutional history because it preserves the tool that preserves Debian systems.

Adoption history

dpkg's direct adoption follows Debian and its derivatives. The official Debian history describes Debian as a large volunteer distribution, and the dpkg homepage points to downstream distributions and distribution-provided packages as the normal way to obtain current dpkg releases.

In everyday use, many users interact with apt, aptitude, or graphical package managers first, but dpkg remains the local authority for .deb package installation state, package database operations, maintainer-script execution, and low-level package queries. Its command suite appears on Debian, Ubuntu, and other systems that need .deb tooling, and it is also packaged by non-Debian systems for compatibility and build workflows.

How it is used

The dpkg manpage describes dpkg as the Debian package manager. It installs, removes, and inspects packages, maintains information about available and installed packages, and can act as a frontend to dpkg-deb and dpkg-query for supported actions.

The wider dpkg package includes developer-facing commands such as dpkg-buildpackage, dpkg-source, dpkg-shlibdeps, dpkg-gensymbols, dpkg-architecture, dpkg-buildflags, and dpkg-parsechangelog, which makes it both a system package manager component and a build-tool suite for Debian packaging.

Why package nerds care

dpkg is one of the canonical package-nerd tools because it embodies the .deb model: control files, package states, maintainer scripts, conffiles, triggers, diversions, alternatives, source packages, build metadata, and dependency-aware system upgrades. For Debian-family systems, apt is the friendly planner, but dpkg is the local executor and database.

Its significance is also cultural. Debian's policy-heavy, source-package-oriented packaging ecosystem depends on dpkg behavior and companion tools. Changes to dpkg ripple into bootstrapping, cross-building, reproducible builds, multiarch behavior, maintainer scripts, and downstream distributions.

Timeline

• 1993: Debian Project officially founded by Ian Murdock.
• 2004: dpkg history file records the end of CVS-only maintenance around dpkg 1.10.24 and the move toward Arch.
• 2006: dpkg history file records Subversion maintenance beginning on 18 January 2006.
• 2007: dpkg history file records Git maintenance beginning on 25 July 2007.
• 2025: Debian Wiki records the Dpkg team page as last modified in August 2025, listing current infrastructure, documentation, and project areas.

Related projects

• dpkg is closely related to apt and other package-manager frontends, dpkg-deb, dpkg-query, dpkg-dev, debhelper, Debian Policy, Debian source packages, and Debian derivatives such as Ubuntu. The dpkg team page also names dpkg-repack, dpkg-www, debsig-verify, dupload, and dlocate as related maintained projects.

Sources

• https://www.dpkg.org/ - official dpkg homepage for project identity, downloads, source repositories, docs, specs, and downstream references.
• https://wiki.debian.org/Teams/Dpkg - official Debian Wiki team page for role, source repository, related tools, docs, and project infrastructure.
• https://www.dpkg.org/history/dpkg-history.txt - official dpkg history note for CVS, Arch, Subversion, and Git maintenance eras.
• https://www.debian.org/doc/manuals/project-history/intro.en.html - official Debian project history for Debian's founding and packaging culture.
• https://www.debian.org/doc/manuals/project-history/manifesto.en.html - official Debian Manifesto text and date.
• https://manpages.debian.org/bookworm/dpkg/dpkg.1.en.html - official Debian manpage for dpkg behavior and related tools.
• https://manpages.debian.org/bookworm/dpkg/dpkg.cfg.5.en.html - official Debian manpage for dpkg configuration files.