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

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