Red Hat Package Manager

Red Hat Package Manager
™/®Red Hat, Inc. · Public domain · source
Name	Red Hat Package Manager
Developer	Red Hat
Released	1997
Latest release version	(varies)
Operating system	Unix-like
License	GNU General Public License

Red Hat Package Manager is a package management system and archive format used on many Unix-like operating systems. Originally created by Red Hat, Inc. engineers, it provides installation, upgrade, query, verification, and removal of software packages and integrates with system tools and distribution projects. RPM has influenced numerous projects and distributions and interacts with a broad ecosystem of build, signing, and repository technologies.

History

The RPM format originated during the 1990s at Red Hat, Inc. as part of early Linux distribution development, contemporaneous with projects such as Debian, Slackware, and SuSE. Key contributors included engineers from Red Hat, Inc. and community members connected to initiatives like the Free Software Foundation and the Open Source Initiative. RPM development paralleled milestones such as the release of Linux kernel updates, the rise of Fedora Project, and the establishment of vendor distributions like CentOS and Oracle Linux. Over time RPM incorporated features influenced by package policies from GNU Project participants, build tooling used in Autotools and CMake, and signing practices from public-key systems championed by the Internet Engineering Task Force. Forks and variants emerged in relation to governance debates, vendor priorities, and collaborations with projects such as SUSE and community distributions like Mageia and AlmaLinux. RPM’s evolution interacted with standards work from organizations such as the Linux Foundation and adoption by enterprise vendors including IBM after mergers and partnerships.

Architecture and file format

RPM packages are cpio archives wrapped with headers and metadata that record payload, scripts, and file attributes; this design reflects archive formats used in early UNIX distributions and tools like cpio and tar. The package header contains structured metadata fields analogous to schema efforts in projects from the Open Source Initiative and standardization discussions within the IETF. RPM supports multiple compression algorithms familiar to GNU Project utilities, and file attributes map to POSIX features used by System V-influenced systems and implementations of the Filesystem Hierarchy Standard employed by distributions such as Red Hat Enterprise Linux and Fedora. The format exposes scriptlet hooks executed at lifecycle events, a design refined alongside installer projects like Anaconda (installer) and configuration management tools used in environments run by organizations such as NASA and CERN.

Package management tools and commands

Command-line tools and front-ends developed around the RPM format include utilities with responsibilities for low-level operations and higher-level transaction management. Tools such as the RPM CLI are used alongside dependency solvers and front-ends inspired by projects like YUM and successors that integrated with Python ecosystems and DNF implementations used in distributions such as Fedora, CentOS Stream, and Red Hat Enterprise Linux. Graphical front-ends and management consoles have been developed for desktop projects like GNOME and KDE, and enterprise management integrates with systems used by Puppet and Ansible automation in infrastructures run by companies like Google and Microsoft in hybrid environments. Build tools such as rpmbuild and macros are part of software packaging workflows that parallel continuous integration systems used in projects like Jenkins and Travis CI.

Package database and metadata

RPM maintains a local package database that indexes installed packages, file lists, checksums, and scriptlet states; the database design evolved alongside database engines used by projects such as SQLite and management practices from Oracle Corporation environments. Metadata fields include names, versions, epochs, releases, architectures, and provides/requires relationships that support dependency resolution compatible with solver strategies found in tools like libsolv. Package signing metadata ties into public-key infrastructures championed by organizations such as RSA Security and standards efforts from the IETF and OpenPGP work driven by communities including the Free Software Foundation. The database enables queries used by system auditing tools employed by compliance programs such as those in FISMA and corporate policies at enterprises like Amazon Web Services.

Repositories and signing

RPM repositories are collections of packages served via web servers, CDN infrastructures, and mirror networks coordinated by projects and vendors such as Fedora Project, CentOS, EPEL, and Red Hat, Inc.. Repository metadata (repodata) and signing practices use approaches compatible with OpenPGP and key management systems similar to those promoted by Cloudflare and Let’s Encrypt for transport security. Repository management tooling integrates with continuous delivery pipelines used by GitLab and GitHub-based projects and with content delivery strategies employed by major vendors such as Microsoft and IBM when distributing enterprise images. Mirror networks and content synchronization rely on protocols and services from Apache HTTP Server and nginx deployments.

RPM-based distributions and ecosystem

Numerous distributions are built on the RPM format, including vendor and community projects such as Red Hat Enterprise Linux, Fedora, CentOS Stream, openSUSE, SUSE Linux Enterprise, Oracle Linux, AlmaLinux, and Scientific Linux. The broader ecosystem includes packaging communities like EPEL, build systems such as Koji, third-party repositories maintained by organizations like MariaDB Corporation and NVIDIA, and integration with container platforms such as Docker and Podman used in orchestration with Kubernetes clusters managed by companies like Google and Red Hat, Inc.. RPM’s role in enterprise, research, and cloud infrastructures connects it to large vendors and projects including IBM, Amazon Web Services, Microsoft Azure, and research organizations like CERN.

Category:Package management