Git commit 15669c6499756235f576db62a951157b79f6375c by Luigi Toscano. Committed on 04/07/2018 at 22:30. Pushed by ltoscano into branch 'master'.
doc: it's the software that's being built Most of the time the sentences revolve around any software by KDE. In one case the sentence is about Plasma specifically. M +10 -10 doc/index.docbook https://commits.kde.org/kdesrc-build/15669c6499756235f576db62a951157b79f6375c diff --git a/doc/index.docbook b/doc/index.docbook index 1f169cd..f1ccd08 100644 --- a/doc/index.docbook +++ b/doc/index.docbook @@ -269,7 +269,7 @@ does not cover this installation type, since we assume you know what you are doi </sect2> <sect2 id="before-building-preparation"> -<title>Ensure your system is ready to build &kde; source</title> +<title>Ensure your system is ready to build &kde; software</title> <para>Before using the &kdesrc-build; script (or any other building strategy) you must install the development tools and libraries needed for &kde;. @@ -545,7 +545,7 @@ it is a good idea to at least load the &kde; project metadata.</para> <title>Loading project metadata</title> <para> -From a terminal window, log in to the user you are using to compile &kde; and +From a terminal window, log in to the user you are using to compile &kde; software and execute the script: </para> <screen> @@ -627,8 +627,8 @@ Your logs are saved in /home/kde-src/kdesrc/log/2018-01-20-07 <para> Depending on how many modules you are downloading, it is possible that -&kdesrc-build; will not succeed the first time you compile &kde;. Do not -despair! +&kdesrc-build; will not succeed the first time you compile &kde; software. +Do not despair! </para> <para>&kdesrc-build; logs the output of every command it runs. By default, @@ -660,7 +660,7 @@ to mail the <email>kde-de...@kde.org</email> mailing list (subscription may be required first) in order to report the build failure.</para> <para>You can find more common examples of things that can go wrong and their -solutions, as well as general tips and strategies to build &kde; in the +solutions, as well as general tips and strategies to build &kde; software in the <ulink url="https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source"> Build from Source</ulink>. </para> @@ -742,9 +742,9 @@ linkend="conf-include-dependencies">include-dependencies</link> option). <title>Setting the Environment to Run Your &kde; &plasma; Desktop</title> <para> -Assuming you are using a dedicated user to build &kde;, and you already have an -installed &kde; version, running your new &kde; may be a bit tricky, as the new -&kde; has to take precedence over the old. You must change the environment +Assuming you are using a dedicated user to build &kde; &plasma;, and you already have an +installed &plasma; version, running your new &plasma; may be a bit tricky, as the new +&plasma; has to take precedence over the old. You must change the environment variables of your login scripts to make sure the newly-built desktop is used. </para> @@ -1295,7 +1295,7 @@ distribution). <listitem><para> &kdesrc-build; does not require a <acronym>GUI</acronym> present to operate. So, -you can build &kde; without needing an alternate graphical environment. +you can build &kde; software without needing a graphical environment. </para></listitem> <listitem><para> @@ -2644,7 +2644,7 @@ installed. </para> <para>Note that using this option can have a significant detrimental impact on -both your bandwidth usage (if you use <replaceable>all</replaceable>) and the time taken to compile &kde;, +both your bandwidth usage (if you use <replaceable>all</replaceable>) and the time taken to compile &kde; software, since &kdesrc-build; will be unable to perform incremental builds.</para> </entry> </row>