No edit summary |
No edit summary |
||
| Line 44: | Line 44: | ||
<abbr Title="dnf [options] reinstall <package-specs>... Installs the specified packages, fails if some of the packages are either not installed or not available (i.e. there is no repository where to download the same RPM).">reinstall</abbr> | <abbr Title="dnf [options] reinstall <package-specs>... Installs the specified packages, fails if some of the packages are either not installed or not available (i.e. there is no repository where to download the same RPM).">reinstall</abbr> | ||
<abbr Title="dnf [options] remove <package-specs>... Removes the specified packages from the system along with any packages depending on the packages being removed. Each <spec> can be either a <package-spec>, which specifies a package directly, or a @<group-spec>, which specifies an (environment) group which contains it. If clean_requirements_on_remove is enabled (the default) also removes any dependencies that are no longer needed.">remove</abbr> | |||
<abbr Title="dnf [options] repolist [enabled|disabled|all] Depending on the exact command, lists enabled, disabled or all known repositories. Lists all enabled repositories by default. Provides more detailed information when -v option is used. This command by default does not force a sync of expired metadata.">repolist</abbr> | |||
<abbr Title="The repository-packages command allows the user to run commands on top of all packages in the repository named <repoid>. However, any dependency resolution takes into account packages from all enabled repositories. Specifications <package-name-spec> and <package-spec> further limit the candidates to only those packages matching at least one of them. info subcommand lists description and summary information about packages depending on the packages’ relation to the repository. list subcommand just dumps lists of that packages. See detailed description in Command Reference (see bellow)">repository-packages</abbr> | |||
<abbr Title="dnf [options] search [all] <keywords>... Search package metadata for the keywords. Keywords are matched as case-insensitive substrings, globbing is supported. By default the command will only look at package names and summaries, failing that (or whenever all was given as an argument) it will match against package descriptions and URLs. The result is sorted from the most relevant results to the least. This command by default does not force a sync of expired metadata.">search</abbr> | |||
<abbr Title="dnf [options] updateinfo [<output>] [<availability>] [<spec>...] Display information about update advisories. Depending on <output>, DNF displays just counts of advisory types (omitted or summary), list of advisories (list) or detailed information (info). When info with -v option is used, the information is even more detailed. <availability> specifies whether advisories about newer versions of installed packages (omitted or available), advisories about equal and older versions of installed packages (installed), advisories about newer versions of those installed packages for which a newer version is available (updates) or advisories about any versions of installed packages (all) are taken into account. Most of the time, available and updates displays the same output. The outputs differ only in the cases when an advisory refers to a newer version but there is no enabled repository which contains any newer version. If given and if neither ID, type (bugfix, enhancement, security/sec) nor a package name of an advisory does match <spec>, the advisory is not taken into account. The matching is case-sensitive and in the case of advisory IDs and package names, globbing is supported.">updateinfo</abbr> | |||
<abbr Title="dnf [options] upgrade Updates each package to a highest version that is both available and resolvable. dnf [options] upgrade <package-installed-specs>... Updates each specified package to the latest available version. Updates dependencies as necessary.">upgrade</abbr> | |||
<abbr Title="dnf [options] upgrade-to <package-nevr-specs>... Upgrades packages to the specified versions.">upgrade-to</abbr> | |||
== Installation == | == Installation == | ||
Revision as of 10:41, 29 September 2015
DNF is a software package manager that installs, updates, and removes packages on RPM-based Linux distributions. It automatically computes dependencies and figures out what things should occur to install packages. DNF makes it easier to maintain groups of machines without having to manually update each one using rpm.
DNF is the next upcoming major version of Yum. It roughly maintains CLI compatibility with Yum and defines strict API for extensions and plugins. Plugins can modify or extend features of DNF or provide additional CLI commands on top of those mentioned below. If you know the name of such a command (including commands mentioned bellow), you may find/install the package which provides it using the appropriate virtual provide in the form of dnf-command(<alias>) where <alias> is the name of the command; e.g. dnf-command(repoquery) for a repoquery command (the same applies to specifying dependencies of packages that require a particular command).
| DNF | |
| |
| RPM package | dnf
|
| Added in | Fedora 18, and later versions |
| Website | http://dnf.baseurl.org/ |
| Bugs • Bodhi • Koji | |
Available commands
autoremove
check-update
clean
distro-sync
downgrade
group
help
history
info
install
list
makecache
mark
provides
reinstall
remove
repolist
repository-packages
search
updateinfo
upgrade
upgrade-to
Installation
DNF comes with Fedora since version 18, but DNF can installed by using the Yum Command:
# yum install dnf
As of Fedora 22, Yum has been replaced with DNF and doesn't need to be install.
Usage
In the basic methods, dnf can be used almost exactly as YUM:
# sudo dnf search audacity
# sudo dnf install audacity.x86_64
# sudo dnf remove audacity
Documentation
https://github.com/rpm-software-management/dnf/wiki lists two documentation links