[sdk/kdesrc-build/docbook_historied_per_file] doc/kdesrc-buildrc: Teach the 'prefix' option to understand ${MODULE}/$MODULE.

[Raphael Kubo da Costa]

Git commit fad747a597e347f67a0a7ca3c9b525b15d8e4b6d by Raphael Kubo da Costa.
Committed on 17/12/2011 at 01:53.
Pushed by ashark into branch 'docbook_historied_per_file'.

Teach the 'prefix' option to understand ${MODULE}/$MODULE.

This commit should make the 'prefix' option expand this variable to the
module's name, so one can easily install each module into a different
directory.

Reviewed-by: mpyne

Original commit: 9be64e86
https://invent.kde.org/sdk/kdesrc-build/-/commit/9be64e86e202f66d07dd4c00b14a76279c8a1196

M  +4    -2    doc/kdesrc-buildrc/conf-options-table.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/fad747a597e347f67a0a7ca3c9b525b15d8e4b6d

diff --git a/doc/kdesrc-buildrc/conf-options-table.docbook b/doc/kdesrc-buildrc/conf-options-table.docbook
index b08d71df..2e370e32 100644
--- a/doc/kdesrc-buildrc/conf-options-table.docbook
+++ b/doc/kdesrc-buildrc/conf-options-table.docbook
@@ -525,11 +525,13 @@ cannot figure out what you mean using <link linkend="conf-branch">branch</link>.
 <row id="conf-prefix">
 <entry>prefix</entry>
 <entry>Module setting overrides global</entry>
-<entry>This option controls where to install the module (normally the
+<entry><para>This option controls where to install the module (normally the
 <option><link linkend="conf-kdedir">kdedir</link></option> setting is used).
 Using this option allows you to install a module to a different directory than
 where the KDE Platform libraries are installed, such as if you were using
-&kdesrc-build; only to build applications.
+&kdesrc-build; only to build applications.</para>
+<para>You can use <varname>${MODULE}</varname> or <varname>$MODULE</varname>
+in the path to have them expanded to the module's name.</para>
 </entry>
 </row>