LEARN. PRACTICE. GROW.Concept and mechanism
Installed package inventory and repository lists answer different questions. rpm -qa shows installed RPM packages; dnf repolist helps inspect configured and available repositories according to the selected options. If an executable is missing, dnf provides can look for the package supplying a path or pattern in available metadata. Results depend on accessible repositories and metadata. Before installation, confirm origin, version, dependencies, and transaction impact. A name appearing in search results does not by itself authorize changing a production server.
Guided application
Current RHCSA objectives also include Flatpak. A Flatpak application has an identifier and is obtained through a remote; do not assume that identifier corresponds to an RPM package name. Inspect remotes and the intended application, confirm the approved origin, and record how it was installed. On an administration workstation, the graphical application and system tools can have different update lifecycles. At handover, document installation mechanism, version, and ownership for each component. Removal must consider dependencies and data as well as the menu’s visible name.
For a missing command, distinguish “which package supplies it?” from “is it installed?”. For a Flatpak application, start with the documented remote and identifier.
Common pitfalls
Confusing inventory with repositories; installing from an unreviewed origin; treating Flatpak IDs as RPM names.
Related topics: Operations, targets, and persistent evidence · Storage, mounts, and persistent identity
Choose the correct mechanism and retain software provenance.
Reference: RHEL10 Flatpak applications · EX200 based on Red Hat Enterprise Linux 10