{"id":114940,"date":"2024-04-09T09:30:54","date_gmt":"2024-04-09T07:30:54","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/v-fedora-41-utverzhdyon-perehod-na-paketnyj-menedzher-dnf5"},"modified":"2024-04-09T09:30:54","modified_gmt":"2024-04-09T07:30:54","slug":"v-fedora-41-utverzhdyon-perehod-na-paketnyj-menedzher-dnf5","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/v-fedora-41-utverzhdyon-perehod-na-paketnyj-menedzher-dnf5","title":{"rendered":"Fedora 41 approves the transition to the DNF5 package manager","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The FESCo (Fedora Engineering Steering Committee), responsible for the technical aspects of the Fedora Linux distribution, has approved the default use of the DNF5 package manager in the upcoming Fedora 41 release. The dnf, libdnf, and dnf-cutomatic packages will be replaced in Fedora 41 by the DNF5 toolkit and a new libdnf5 library, while the symbolic link \/usr\/bin\/dnf will begin to point to the dnf5 executable. <\/p>\n
Although complete parity in functionality with the old tools has not yet been achieved, developers believe that the distribution is ready for migration, and the missing capabilities can be implemented later. For example, the functionality related to transaction history management, which underpins the \"dnf history\" command, is currently unavailable. Additionally, work on integrating support for the background process dnf5daemon into the GNOME Software application manager is still incomplete. More testing is required for the system update mechanism to the next release (the system-upgrade command). <\/p>\n
DNF replaced the Yum package manager in the distribution, which was entirely written in Python. In DNF, performance-critical low-level functions were rewritten and moved to separate C libraries, such as hawkey, librepo, libsolv, and libcomps, while the framework and high-level components remained in Python. The DNF5 project aims to unify the existing low-level libraries, rewrite the remaining Python package management components in C++, and move the core functionality to a separate libdnf5 library, creating wrappers around this library to maintain the Python API. <\/p>\n
Using C++ instead of Python has eliminated a large number of dependencies, reduced the size of the tooling, and increased performance. Higher performance is achieved not only through compilation to machine code but also due to an improved implementation of the transaction table, optimized repository loading, and restructuring of the database (separating the system state databases and operation history). The DNF5 tooling is independent of PackageKit, which has been replaced by a new background process called DNF Daemon, taking over PackageKit's functionality and providing an interface for managing packages and updates in graphical environments. <\/p>\n
The overhaul has also made it possible to implement some improvements that enhance the usability of the package manager. For instance, the new DNF features a more visual indication of operation progress; it adds support for local RPM packages in transactions; it allows reports on completed transactions to display information provided by scripts embedded in the packages (scriplets); and it proposes an advanced input auto-completion system for bash. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"