Software architecture
PackageKit runs as a system-activated daemon, namedpackagekitd
, which abstracts out differences between the different systems. A library called libpackagekit
allows other programs to interact with PackageKit.
Features include:
* installing local files, ServicePack media and packages from remote sources
* authorization using Polkit
* the use of existing packaging tools
* multi-user system awareness – it will not allow shutdown in critical parts of the transaction
* a system-activated daemon which exits when not in use
Front-ends
*pkcon
is the official front-end of PackageKit, it operates from the command line.
GTK-based:
* gnome-packagekit is an official GNOME front-end for PackageKit. Unlike GNOME Software, gnome-packagekit can handle all packages, not just applications, and has advanced features that are missing in GNOME Software as of June 2020.
* GNOME Software is a utility for installing the applications and updates on Linux. It is part of the GNOME Core Applications and was introduced in GNOME 3.10.
Qt-based:
Back-ends
A number of different package management systems (known as back-ends) support different abstract methods and signals used by the front-end tools. Supported back-ends include: * Advanced Packaging Tool (APT) * Conary * libdnf & librepo, the libraries upon which DNF, (the successor to yum) builds * Entropy * Opkg * pacman * PiSi * Portage * Smart Package Manager * urpmi * YUM * ZYppSee also
* AppStream * Listaller * Polkit * Red Carpet * Software Updater * List of Linux package management systemsReferences
External links
* {{DEFAULTSORT:Packagekit Applications using D-Bus Free package management systems Free software programmed in C Free software programmed in C++ Free software programmed in Python Linux package management-related software Linux PMS graphical front-ends Package management software that uses GTK Package management software that uses Qt Software using the GNU General Public License