DNF (A. Yum is dead, DNF)

Yum had not learned it, and suddenly heard it was going to be abandoned.

In the latest version of Fedora 22, the Yum Package Manager was discarded and replaced by DNF.

Then search Fedora Release Note.

The authorities gave explanations and some changes.

In the latest Fedora 22 test, the basic installation update usage has not changed much.

Previously installed yum install httpd, became DNF install httpd

The following is an official document that has time to translate slowly.

3.6.1. Yum replaced by dnftheYum Package Manager have been replaced in Fedora for successor, DNF. The Yum Fork have been available in Fedora for testing since Fedora, and are now the default command line package Manager .Most DNF commands use directives is familiar to Yum users, and it uses the same RPM package repositories. Behind The scenes, DNF uses an improved dependency solver,Hawkey, along with Librepo for repository operations and Libcomps for package groups. The /usr/bin/yumCommand would redirect to /usr/bin/dnfand print a warning about the redirection. The Legacy Yum Package Manager can manually installed; The Legacy command line utility have been renamed to yum-deprecated. Read more about using dnf! Consult the upstream documentation athttp://dnf.readthedocs.org/en/latest/index.html. Extra plugins is documented at https://rpm-software-management.github.io/dnf-plugins-extras/index.htmThe behavior of DNF differs from the Yum in some areas:3.6.1.1. Updates that Don's work was skippedif a portion of a transaction is not viable, DNF would automatically exclude it and Tran Sparently continue with the portions that would work. For example, if a package has unmet dependencies during a dnf updateAction, which package is not being updated, but others would. This was similar to Yum ' s --skip-brokendirective, but evaluates the impact of the problem against the entire transaction. Because The default behavior, there is no --skip-brokenSwitch for DNF. To reveal details on a problematic package direction, you can use the --bestOption. dnf update --bestWould force DNF to resolve the transaction using the latest versions of involved packages, and report any problems instead of skipping them. Equivalent to Yum ' s behavior without --skip-broken.3.6.1.2. Repos that don ' t work is SKIPPEDIF a configured and enabled repository does not respond,DNF would skip it and continue the transaction with the available repos. This differs from Yum, which would immediately stop if a repository is not available.3.6.1.3. Update and Upgrade are the samethe commands dnf updateand dnf upgradeis equivalent. This differs from Yum, where yum upgradeWould has the same effect as yum update --obsoletes, and take obsolete packages into account.3.6.1.4. Dependencies is not upgraded in package Installationwhen installing a new package, previously installed Dependencies would Not being upgraded. Yum offered an option for this behavior, upgrade_requirements_on_install. To upgrade with DNF, use dnf update. If DNF reports that dependencies on installed packages is unmet while installing a new package, update the dependent pack Ages before trying again.3.6.1.5. Removewhen Removing a package, DNF would automatically remove any dependent packages that were not explicitly inst Alled by the user. If A package is independently installed, it won ' t be uninstalled the this. Only packages installed as dependencies is removed. This behavior was configured by the clean_requirements_on_removeoption in /etc/dnf/dnf.conf3.6.1.6. Repo cache Refresh Scheduleby default, DNF would check for updates in configured repositories hourly, starting ten Minutes after the system boots. The action is controlled by a SYSTEMD timer unit, /usr/lib/systemd/system/dnf-makecache.timer. To adjust this, copy the timer file to /etc/systemd/system/dnf-makecache.timerand edit it. Alternatively, setting the metadata_timer_syncInch /etc/dnf/dnf.confTo a number of seconds configures the minimum number of seconds between makecache operations. If the timer has not expired, dnf makecacheWould exit IMMEDIATELY.DNF would also honor the Metadata_expire option set in individual repo configs, and refresh repo meta Data at runtime if it's too old. This option was described in man yum.conf.3.6.1.7. Repository actionsthe repository-packagesdirective can used to search for or get info about packages in a specific repository, list installed packages from that Repository, and more. This simplifies operations that would has required use of --excluderepoand --includerepoOptions with Yum, and are especially useful for managing similar packages from different repositories.3.6.1.8. Listing Dependenciesto Find out who package supplies a particular provide, use the dnf provides fooCommand. This replaces yum resolvedep foo. To list the dependencies of a dnf repoquery --requires foo. This replaces yum deplist foo.3.6.1.9. DNF would remove kernelskernel packages is not protected by DNF. Unlike with Yum, you can remove all kernel packages, including the running package, if you direct it to. Be cautious with removing kernels, and specify the full version and release when removing them for best results.3.6.1.10. Replacing Packageswhen A system requires the capabilities of a package for you want to replace, use the --allowerasingOption. For example, dnf --allowerasing mariadbWould allow you to replace MySQL with mariadb, without disrupting packages that require capabilities provided by both Packa Ges. This replaces yum shelland yum swapfunctionality.3.6.1.11. DNF langpacks PLUG-INDNF supports installing language packs using the dnf-langpacksPlug-in, which is expected to work identically to the older yum-langpacksPlug-in. See sections 4.3.3, "DNF langpacks plug-in" for details.3.6.1.12. Support for disabled repositoriesthe software tool and PackageKit Now, searching for packages in disabled repositories. If A, user searches for a, package using one of these applications and the. Found in a repository which includes T He line enabled_metadata=1In its definition, a dialog window would be displayed informing the user that the package had been found, but an additional Repository must is enabled before it can be installed. The same message can also inform the user about the reason, the repository is disabled by default. This change allows Fedora remixes to ship pre-configured but disabled repositories for any reason-for example, if said R Epositories contain non-free software. Fedora itself does not has any such repositories pre-configured; Therefore this feature won't is visible on a Fedora installation unless you specifically configure one or more repos Itories with the enabled_metadata=1Statement.

DNF (A. Yum is dead, DNF)