What the RPM Package Manager is
RPM is the package management system maintained at rpm.org: it defines the .rpm package format and the tooling that installs, verifies, upgrades and removes packages rpm.org2026-08. Each package carries metadata (name, version, architecture, dependencies, cryptographic signature) alongside the payload, and the RPM database on an installed system records every package's files, which is what makes clean upgrades and verification possible. Originally "Red Hat Package Manager", the project renamed itself recursively as adoption spread beyond Red Hat.
Who uses it, and the .deb divide
| Family | Distributions | High-level tool |
|---|---|---|
| RPM (Red Hat lineage) | RHEL, Fedora, CentOS Stream, AlmaLinux, Rocky | dnf (formerly yum) |
| RPM (SUSE lineage) | openSUSE, SUSE Linux Enterprise | zypper |
| Debian format (.deb) | Debian, Ubuntu, Mint | apt |
The commands
Fedora's quick docs cover day-to-day usage Fedora quick docs2026-08; the essentials:
# install with dependency resolution (Fedora / RHEL family)
sudo dnf install ./package.rpm
# openSUSE equivalent
sudo zypper install ./package.rpm
# inspect a package without installing
rpm -qip package.rpm # metadata
rpm -qlp package.rpm # file list
# verify an installed package against the database
rpm -V packagenameUse dnf or zypper rather than bare rpm -i for installs: the low-level tool does not resolve dependencies, and unresolved dependencies are the classic first frustration with hand-installed packages.
When a non-Linux developer meets one
Typically via a vendor download page offering .deb and .rpm side by side, a CI pipeline building Linux artifacts, or a server handover. On Windows or macOS an .rpm is inspectable (7-Zip and similar open the archive) but not installable; the practical routes are the vendor's native build, a container image, or a VM. If you arrived here meaning the dashboard metric or the tachometer, the fork back is what RPM stands for.