[system-administrators-guide] Variables can only be used in config files
stephenw
stephenw at fedoraproject.org
Tue Jun 9 20:15:41 UTC 2015
commit f904ffd644aa2347e83fbeea43a6ac897033ce12
Author: Stephen Wadeley <swadeley at redhat.com>
Date: Tue Jun 9 22:10:22 2015 +0200
Variables can only be used in config files
update as per Michal Luscon
en-US/DNF.xml | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
---
diff --git a/en-US/DNF.xml b/en-US/DNF.xml
index a929a31..655ee3c 100644
--- a/en-US/DNF.xml
+++ b/en-US/DNF.xml
@@ -1046,11 +1046,11 @@ ID | Login user | Date a | Action | Altere
set options for individual repositories by editing the <literal>[<replaceable>repository</replaceable>]</literal> sections in <filename>/etc/dnf/dnf.conf</filename> and <filename class="extension">.repo</filename> files in the <filename class="directory">/etc/yum.repos.d/</filename> directory;
</para>
</listitem>
- <!--<listitem>
+ <listitem>
<para>
use DNF variables in <filename>/etc/dnf/dnf.conf</filename> and files in the <filename>/etc/yum.repos.d/</filename> directory so that dynamic version and architecture values are handled correctly;
</para>
- </listitem>-->
+ </listitem>
<listitem>
<para>
add, enable, and disable DNF repositories on the command line; and,
@@ -1262,14 +1262,14 @@ baseurl=<replaceable>repository_url</replaceable></programlisting>
<secondary>variables</secondary>
</indexterm>
<para>
- You can use and reference the following built-in variables in <command>dnf</command> commands<!-- and in all DNF configuration files (that is, <filename>/etc/dnf/dnf.conf</filename> and all <filename class="extension">.repo</filename> files in the <filename class="directory">/etc/yum.repos.d/</filename> directory)-->:
+ Variables can be used only in the appropriate sections of the DNF configuration files, namely the <filename>/etc/dnf/dnf.conf</filename> file and all <filename class="extension">.repo</filename> files in the <filename class="directory">/etc/yum.repos.d/</filename> directory. Repository variables include:
</para>
<variablelist>
<varlistentry>
<term><varname>$releasever</varname></term>
<listitem>
<para>
- You can use this variable to reference the release version of &MAJOROS;. DNF obtains the value of <varname>$releasever</varname> from the <package>redhat-release</package> package.
+ Refers to the release version of operating system which DNF derives from information available in RPMDB.
</para>
</listitem>
</varlistentry>
@@ -1277,7 +1277,7 @@ baseurl=<replaceable>repository_url</replaceable></programlisting>
<term><varname>$arch</varname></term>
<listitem>
<para>
- You can use this variable to refer to the system's CPU architecture. It is initialized with a value provided by the <systemitem>hawkey</systemitem> library. Valid values for <varname>$arch</varname> include: <literal>i586</literal>, <literal>i686</literal> and <literal>x86_64</literal>.
+ Refers to the system’s CPU architecture. Valid values for <varname>$arch</varname> include: <literal>i586</literal>, <literal>i686</literal> and <literal>x86_64</literal>.
</para>
</listitem>
</varlistentry>
@@ -1285,7 +1285,7 @@ baseurl=<replaceable>repository_url</replaceable></programlisting>
<term><varname>$basearch</varname></term>
<listitem>
<para>
- You can use <varname>$basearch</varname> to reference the base architecture of the system. For example, i686 and i586 machines both have a base architecture of <literal>i386</literal>, and AMD64 and Intel64 machines have a base architecture of <literal>x86_64</literal>.
+ Refers to the base architecture of the system. For example, i686 and i586 machines both have a base architecture of <literal>i386</literal>, and AMD64 and Intel64 machines have a base architecture of <literal>x86_64</literal>.
</para>
</listitem>
</varlistentry>
More information about the docs-commits
mailing list