[doc] Describe relation of dnf.conf with defaults in conf (RhBug:1738…

…837)

Options skip_if_unavailable and best are shipped with different defaults
for particular distributions. Defaults are adjusted by different content
of dnf.conf. The patch mentions the situation for those two options.

https://bugzilla.redhat.com/show_bug.cgi?id=1738837

doc/api_conf.rst

@@ -30,7 +30,10 @@ Configurable settings of the :class:`dnf.Base` object are stored into a :class:`
 
   .. attribute:: best
 
-    Boolean option, ``True`` instructs the solver to either use a package with the highest available version or fail. On ``False``, do not fail if the latest version can not be installed. Default is ``True``.
+    Boolean option, ``True`` instructs the solver to either use a package with the highest available
+    version or fail. On ``False``, do not fail if the latest version can not be installed. Default
+    is ``False``. The default can be overridden by :ref:`DNF configuration file <conf_ref-label>`
+    that could differ for particular distribution.
 
   .. attribute:: cachedir
 
@@ -186,7 +189,8 @@ Configurable settings of the :class:`dnf.Base` object are stored into a :class:`
 
     If enabled, DNF will continue running and disable the repository that couldn't be synchronized
     for any reason. This option doesn't affect skipping of unavailable packages after dependency
-    resolution. The default is ``False``.
+    resolution. The default is ``False``. The default can be overridden by
+    :ref:`DNF configuration file <conf_ref-label>` that could differ for particular distribution.
 
   .. attribute:: sslcacert
 

doc/cli_vs_yum.rst

@@ -117,14 +117,15 @@ Also see related Fedora bugzillas `982947
 
 .. _skip_if_unavailable_default:
 
-============================================
- ``skip_if_unavailable`` enabled by default
-============================================
-
-The important system repos should never be down and we see the third-party repos
-down often enough to warrant this change. Note that without this setting and
-without an explicit ``skip_if_unavailable=True`` in the relevant repo .ini file
-YUM immediately stops on a repo error, confusing and bothering the user.
+====================================================
+ ``skip_if_unavailable`` could be enabled by default
+====================================================
+
+In some distribution DNF is shipped with ``skip_if_unavailable=True`` in
+:ref:`DNF configuration file <conf_ref-label>` file. The reason for the change are the third-party
+repository that down often. Note that without this setting and without an explicit
+``skip_if_unavailable=True`` in the relevant repo .ini file YUM immediately stops on a repo error,
+confusing and bothering the user.
 
 See the related `Fedora bug 984483 <https://bugzilla.redhat.com/show_bug.cgi?id=984483>`_.
 

doc/conf_ref.rst

@@ -75,7 +75,8 @@ or :ref:`mirrorlist <mirrorlist-label>` option definition.
     When upgrading a package, always try to install its highest version
     available, even only to find out some of its deps are not
     satisfiable. Enable this if you want to experience broken dependencies in
-    the repositories firsthand. The default is False.
+    the repositories firsthand. The default is ``True``. The default can be overridden by
+    :ref:`DNF configuration file <conf_ref-label>` that could differ for particular distribution.
 
 ``cachedir``
     :ref:`string <string-label>`
@@ -600,6 +601,8 @@ configuration.
     for any reason. This option doesn't affect skipping of unavailable packages after dependency
     resolution. To check inaccessibility of repository use it in combination with
     :ref:`refresh command line option <refresh_command-label>`. The default is ``False``.
+    The default can be overridden by :ref:`DNF configuration file <conf_ref-label>` that could
+    differ for particular distribution.
 
 .. _sslcacert-label: