Blame SOURCES/BZ-1411692-docs-conf-var-naming-rules.patch

5e9bef
diff -up yum-3.4.3/docs/yum.conf.5.orig yum-3.4.3/docs/yum.conf.5
5e9bef
--- yum-3.4.3/docs/yum.conf.5.orig	2017-11-01 14:58:28.259740017 +0100
5e9bef
+++ yum-3.4.3/docs/yum.conf.5	2017-11-01 14:58:48.528648100 +0100
5e9bef
@@ -1356,8 +1356,17 @@ the same name. If the shell environment
5e9bef
 configuration file variable will not be replaced.
5e9bef
 
5e9bef
 .LP
5e9bef
-As of 3.2.28, any file in /etc/yum/vars is turned into a variable named after
5e9bef
-the filename (or overrides any of the above variables).
5e9bef
+When variable names are parsed in a string, all alphanumeric characters and
5e9bef
+underscores immediately following a $ sign are interpreted as part of a name.
5e9bef
+If a variable is undefined, it will not be replaced.
5e9bef
+For example, the strings $releasever-foo or $releasever/foo will be expanded
5e9bef
+with the $releasever value accordingly, whereas $releaseverfoo or
5e9bef
+$releasever_foo will not be expanded.
5e9bef
+
5e9bef
+As of 3.2.28, any properly named file in /etc/yum/vars is turned into
5e9bef
+a variable named after the filename (or overrides any of the above variables).
5e9bef
+Filenames may contain only alphanumeric characters and underscores
5e9bef
+and be in lowercase.
5e9bef
 
5e9bef
 Note that no warnings/errors are given if the files are unreadable, so creating
5e9bef
 files that only root can read may be confusing for users.