Which results in PackageKit requiring up to three times more network bandwidth and data usage to keep the system up-to-date compared to updating with delta RPMs. Libdnf and PackageKit don’t yet support downloading delta RPMs. PackageKit will simply leave the orphaned packages installed and even keep updating them in the future even though the library sits there without any software ever using it. The command-line dnf utility can automatically identify and remove orphaned packages - unused libraries and other packages - when you upgrade or remove software. Problems quickly show up when comparing pkcon and dnf, the command-line interfaces of PackageKit and DNF respectively: It’s worth noting here that both the Pacman backend for Arch Linux and APT backend for Ubuntu seem to be in a much better shape than the DNF backend in PackageKit. In other words: GNOME Software and Plasma Discover, two front-and-center applications for end-users on Fedora Workstation (and the Fedora KDE Plasma Desktop edition), rely on an unfinished work-in-progress library on Fedora Linux. Once major users like PackageKit and DNF are fully ported, a new stable release will be considered. Note that libdnf is currently being reworked and is considered unstable. It relies on the still in-development libdnf library which is a fairly new effort to port DNF from Python to C. However, PackageKit in Fedora Linux isn’t great. That is to say, you can use the same command-line interface - or programming API - for interacting with the host operating system’s package manager regardless of the distribution or underlying package manager. Other package managers and distributions are supported as well. The idea behind PackageKit is to provide a cross-platform front-end and API layer for common operations in popular Linux package managers such as APT for Debian and Ubuntu, DNF for Fedora and RHEL, Zypper for openSUSE and SUSE, and Pacman for Arch Linux. PackageKit is part of the magic that makes GNOME Software Center and KDE Plasma Discovery - the two most widely used “app stores” on Linux - work across different Linux distributions despite each having their own package manager. Here is some of the advantages DNF still gives you over PackageKit based applications. You may be better off sticking with the DNF package manager in the command-line even though PackageKit is the choice of all the graphical package managers. DNF has all the latest features and the best support, but PackageKit is put front and center in GNOME Software, KDE Plasma Discover, and as of Fedora Linux 26 also in Cockpit’s new Software Update panel. Fedora Workstation comes with two package managers by default: DNF and PackageKit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |