commit 63bef7b3d4259b22d31db2d5b8483a2e53034e7b
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Fri Apr 17 17:08:47 2015 +0200
Change Yum to DNF in RPM.xml
en-US/RPM.xml | 20 ++++++++++----------
1 files changed, 10 insertions(+), 10 deletions(-)
---
diff --git a/en-US/RPM.xml b/en-US/RPM.xml
index 35fb303..511b7df 100644
--- a/en-US/RPM.xml
+++ b/en-US/RPM.xml
@@ -19,19 +19,19 @@
The <firstterm>RPM Package Manager</firstterm>
(<application>RPM</application>) is an open packaging system that runs on
&MAJOROS; as well as other Linux and UNIX systems. Red Hat and the Fedora
Project encourage other vendors to use <application>RPM</application> for
their own products. <application>RPM</application> is distributed under the
terms of the <firstterm>GPL</firstterm> (<firstterm>GNU General Public
License</firstterm>).
</para>
<para>
- The <application>RPM Package Manager</application> only works with
packages built in the <emphasis>RPM format</emphasis>.
<application>RPM</application> itself is provided as the pre-installed
<package>rpm</package> package. For the end user,
<application>RPM</application> makes system updates easy. Installing,
uninstalling, and upgrading <application>RPM</application> packages can be
accomplished with short commands. <application>RPM</application> maintains a
database of installed packages and their files, so you can make queries and verify
installed files on your system. There are several applications, such as
<application>Yum</application> or
<application>PackageKit</application>, that can make working with packages in
the <application>RPM</application> format even easier.
+ The <application>RPM Package Manager</application> only works with
packages built in the <emphasis>RPM format</emphasis>.
<application>RPM</application> itself is provided as the pre-installed
<package>rpm</package> package. For the end user,
<application>RPM</application> makes system updates easy. Installing,
uninstalling, and upgrading <application>RPM</application> packages can be
accomplished with short commands. <application>RPM</application> maintains a
database of installed packages and their files, so you can make queries and verify
installed files on your system. There are several applications, such as
<application>DNF</application> or
<application>PackageKit</application>, that can make working with packages in
the <application>RPM</application> format even easier.
</para>
- <warning id="warning-Use_Yum_Instead_of_RPM_Whenever_Possible">
- <title>Use Yum Instead of RPM Whenever Possible</title>
+ <warning id="warning-Use_DNF_Instead_of_RPM_Whenever_Possible">
+ <title>Use DNF Instead of RPM Whenever Possible</title>
<indexterm>
<primary>packages</primary>
- <secondary>Yum instead of RPM</secondary>
+ <secondary>DNF instead of RPM</secondary>
</indexterm>
<para>
- For most package-management tasks, the <application>Yum</application>
package manager offers equal and often greater capabilities and utility than
<application>RPM</application>. <application>Yum</application>
also performs and tracks complicated system-dependency resolutions.
<application>Yum</application> maintains the system integrity and forces a
system integrity check if packages are installed or removed using another application,
such as <application>RPM</application>, instead of
<application>Yum</application>. For these reasons, it is highly recommended
that you use <application>Yum</application> instead of
<application>RPM</application> whenever possible to perform package-management
tasks. See <xref linkend="ch-yum"/>.
+ For most package-management tasks, the <application>DNF</application>
package manager offers equal and often greater capabilities and utility than
<application>RPM</application>. <application>DNF</application>
also performs and tracks complicated system-dependency resolutions.
<application>DNF</application> maintains the system integrity and forces a
system integrity check if packages are installed or removed using another application,
such as <application>RPM</application>, instead of
<application>DNF</application>. For these reasons, it is highly recommended
that you use <application>DNF</application> instead of
<application>RPM</application> whenever possible to perform package-management
tasks. See <xref linkend="ch-DNF"/>.
</para>
<para>
- If you prefer a graphical interface, you can use the
<application>PackageKit</application> GUI application, which uses
<application>Yum</application> as its back end, to manage your system's
packages.
+ If you prefer a graphical interface, you can use the
<application>PackageKit</application> GUI application, which uses
<application>DNF</application> as its back end, to manage your system's
packages.
</para>
</warning>
<para>
@@ -298,7 +298,7 @@
<warning id="warning-Forcing_Package_Installation">
<title>Warning</title>
<para>
- Although you can <emphasis>force</emphasis>
<command>rpm</command> to install a package that has an unresolved dependency
(using the <option>--nodeps</option> option), this is
<emphasis>not</emphasis> recommended and will usually result in the installed
software failing to run. Installing packages with <option>--nodeps</option>
can cause applications to misbehave or terminate unexpectedly. It can also cause serious
package-management problems or system failure. For these reasons, heed the warnings about
missing dependencies. The <application>Yum</application> package manager
performs automatic dependency resolution and fetches dependencies from on-line
repositories.
+ Although you can <emphasis>force</emphasis>
<command>rpm</command> to install a package that has an unresolved dependency
(using the <option>--nodeps</option> option), this is
<emphasis>not</emphasis> recommended and will usually result in the installed
software failing to run. Installing packages with <option>--nodeps</option>
can cause applications to misbehave or terminate unexpectedly. It can also cause serious
package-management problems or system failure. For these reasons, heed the warnings about
missing dependencies. The <application>DNF</application> package manager
performs automatic dependency resolution and fetches dependencies from on-line
repositories.
</para>
</warning>
</section>
@@ -601,7 +601,7 @@ S.5....T. c /etc/abrt/abrt.conf
<primary>packages</primary>
<secondary>initial RPM repositories</secondary>
</indexterm>
- Official <application>RPM</application> repositories provided
with the <application>Yum</application> package manager. See <xref
linkend="ch-yum"/> for details on how to use the official &MAJOROS;
package repositories.
+ Official <application>RPM</application> repositories provided
with the <application>DNF</application> package manager. See <xref
linkend="ch-DNF"/> for details on how to use the official &MAJOROS;
package repositories.
</para>
</listitem>
@@ -642,7 +642,7 @@ S.5....T. c /etc/abrt/abrt.conf
</para>
<synopsis><command>rpmkeys -K
<replaceable>package.rpm</replaceable></command></synopsis>
<para>
- Note that the <application>Yum</application> package manager performs
automatic checking of <application>GPG</application> signatures during
installations and upgrades.
+ Note that the <application>DNF</application> package manager performs
automatic checking of <application>GPG</application> signatures during
installations and upgrades.
</para>
<para>
<application>GPG</application> is installed by default, as well as a
set of Red Hat keys for verifying packages. To import additional keys for use
with <application>RPM</application>, see <xref
linkend="s2-keys-importing"/>.
@@ -822,7 +822,7 @@ S.5....T. c /etc/abrt/abrt.conf
</indexterm>
<listitem>
<para>
- <xref linkend="ch-yum" /> describes how to use the
<application>Yum</application> package manager to search, install, update, and
uninstall packages on the command line.
+ <xref linkend="ch-DNF" /> describes how to use the
<application>DNF</application> package manager to search, install, update, and
uninstall packages on the command line.
</para>
</listitem>
</itemizedlist>