Git commit 42276b71fddd9893f1e016d0b4128f45a9132913 by Burkhard Lück. Committed on 26/05/2016 at 06:32. Pushed by ashark into branch 'docbook_historied_per_file'.
Fix kdesrc-build docbook adapt header to doctools.git / src / templates fix wrong + outdated links use new repo address scheme set date to 16.05 use http://code.qt.io/cgit/qt/ for Qt repo add some fixme's where the docbook seems to be wrong or outdated REVIEW:127820 Original commit: 2d6f3c8a https://invent.kde.org/sdk/kdesrc-build/-/commit/2d6f3c8a5208f91165c0b73de2633d3792686a83 M +1 -1 doc/appendix-modules/module-concept.docbook M +10 -10 doc/getting-started/before-building.docbook M +2 -2 doc/getting-started/building-and-troubleshooting.docbook M +2 -2 doc/getting-started/configure-data.docbook M +3 -3 doc/getting-started/index.docbook M +8 -8 doc/getting-started/kde-modules-and-selection.docbook M +1 -1 doc/index.docbook M +1 -1 doc/kde-cmake/kde-cmake-intro.docbook M +3 -3 doc/kdesrc-buildrc/conf-options-table.docbook [INFRASTRUCTURE] M +1 -1 doc/using-kdesrc-build/advanced-features.docbook M +1 -1 doc/using-kdesrc-build/basic-features.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/42276b71fddd9893f1e016d0b4128f45a9132913 diff --git a/doc/appendix-modules/module-concept.docbook b/doc/appendix-modules/module-concept.docbook index 47ec9dc5..9b874fd2 100644 --- a/doc/appendix-modules/module-concept.docbook +++ b/doc/appendix-modules/module-concept.docbook @@ -4,7 +4,7 @@ <para>&kde; groups its software into <quote>modules</quote> of various size. This was initially a loose grouping of a few large modules, but with the introduction of the <ulink url="http://git-scm.com/">Git</ulink>-based <ulink -url="https://projects.kde.org/">source code repositories</ulink>, these large +url=" https://commits.kde.org/">source code repositories</ulink>, these large modules were further split into many smaller modules. </para> diff --git a/doc/getting-started/before-building.docbook b/doc/getting-started/before-building.docbook index 9cf6f142..1fd82554 100644 --- a/doc/getting-started/before-building.docbook +++ b/doc/getting-started/before-building.docbook @@ -31,8 +31,8 @@ in order to prepare and use the system installation correctly. <para>Before using the &kdesrc-build; script (or any other building strategy) you must install the development tools and libraries needed for &kde;. The nearly complete list of required tools can be found from -the <ulink url="http://techbase.kde.org/Getting_Started/Build/Requirements">KDE -TechBase Build Requirements</ulink> page. +the <ulink url="https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source#Install_required_devel_packages">&kde; +Community Wiki Build Requirements</ulink> page. </para> <para>Here is a list of some of the things you will need:</para> @@ -56,8 +56,8 @@ if you have it by running <userinput><command>svn <listitem><para>You will need the <ulink url="http://gitscm.org/">Git source control manager</ulink> installed as well, for &kde;'s <ulink -url="http://projects.kde.org/">git-based projects.</ulink> -.</para></listitem> +url=" https://commits.kde.org/">git-based projects. +</ulink></para></listitem> <listitem><para>Although it is not required, the <ulink url="http://bazaar.canonical.com/">Bazaar</ulink> source control manager is @@ -68,7 +68,7 @@ build libdbusmenu-qt, you must have Bazaar installed.</para></listitem> </itemizedlist></listitem> -<listitem><para>You will need a full C++ development environment. GCC 4.6 or +<listitem><para>You will need a full C++ development environment. GCC 4.6 or <!--FIXME update? --> later is recommended.</para></listitem> <listitem><para>Finally, you will need a <quote>make</quote> tool. GNU Make is @@ -80,9 +80,9 @@ why it is required.</para></listitem> </itemizedlist> <note><para>Most operating system distributions include a method of easily -installing required development tools. Consult the TechBase <ulink -url="http://techbase.kde.org/Getting_Started/Build/KDE4">Getting Started</ulink> -page's <quote>Required Packages from your Distribution</quote> section to see +installing required development tools. Consult the Community Wiki page <ulink +url="https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source#Install_required_devel_packages" +>Required devel packages</ulink> to see if these instructions are already available.</para></note> <para>One exception to the required libraries is the &Qt; library. @@ -122,8 +122,8 @@ and development packages. You will need at least the program or library <emphasis>and</emphasis> its development package. The libraries you need will change depending on the modules you intend to build, as each module has its own requirements. The <ulink -url="http://techbase.kde.org/Getting_Started/Build/KDE4#Required_packages_from_your_distribution">&kde; -TechBase</ulink> has more details about the specific tools and techniques used +url="https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source">&kde; +Community wiki</ulink> has more details about the specific tools and techniques used to install and find the required software. </para></important> diff --git a/doc/getting-started/building-and-troubleshooting.docbook b/doc/getting-started/building-and-troubleshooting.docbook index b1e2a2e6..2cee55a0 100644 --- a/doc/getting-started/building-and-troubleshooting.docbook +++ b/doc/getting-started/building-and-troubleshooting.docbook @@ -75,8 +75,8 @@ 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 -<ulink url="http://techbase.kde.org/Getting_Started/Build/KDE4"> -Building &kde; 4 from Source</ulink>. +<ulink url="https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source"> +Build from Source</ulink>. </para> <para>On the other hand, assuming everything went well, you should have a new diff --git a/doc/getting-started/configure-data.docbook b/doc/getting-started/configure-data.docbook index 9c6266c3..c28e8fb2 100644 --- a/doc/getting-started/configure-data.docbook +++ b/doc/getting-started/configure-data.docbook @@ -52,8 +52,8 @@ source code. <listitem><para><link linkend="conf-svn-server">svn-server</link>, which selects what &url; to download the sources from. This is useful if you are a -developer with a <ulink url="http://techbase.kde.org/Contribute/First_Steps_with_your_KDE_SVN_Account">&kde; -&subversion; account</ulink>.</para></listitem> +developer with a <ulink url="https://community.kde.org/Infrastructure/First_Steps_with_your_Contributor_Account">&kde; +contributor account</ulink>.</para></listitem> <listitem><para>You will probably want to select different modules to build, which is described in <xref linkend="selecting-modules"/>.</para></listitem> diff --git a/doc/getting-started/index.docbook b/doc/getting-started/index.docbook index 855c3175..f101060d 100644 --- a/doc/getting-started/index.docbook +++ b/doc/getting-started/index.docbook @@ -10,9 +10,9 @@ the script. <para> All topics present in this chapter are covered with even more detail in the -<ulink url="http://techbase.kde.org/Getting_Started/Build/KDE4"> -Building &kde; 4 from Source</ulink> article, at the -<ulink url="http://techbase.kde.org/">&kde; TechBase site</ulink>. +<ulink url="https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source"> +Build from Source</ulink> article, at the +<ulink url="https://community.kde.org/">&kde; Community Wiki</ulink>. If you are compiling &kde; for the first time, it is a good idea to read it, or consult it as a reference source. You will find detailed information about packaging tools and requirements, common compilation pitfalls and diff --git a/doc/getting-started/kde-modules-and-selection.docbook b/doc/getting-started/kde-modules-and-selection.docbook index eedcd576..1eceb74f 100644 --- a/doc/getting-started/kde-modules-and-selection.docbook +++ b/doc/getting-started/kde-modules-and-selection.docbook @@ -11,7 +11,7 @@ select the software modules that you want built. </para> <orderedlist> -<listitem><para>At the lowest level comes Digia's &Qt; library, which is a +<listitem><para>At the lowest level comes the &Qt; library, which is a very powerful, cross-platform <quote>toolkit</quote> library. &kde; is based on &Qt;, and some of the non-&kde; libraries required by &kde; are also based on &Qt;. &kdesrc-build; can build &Qt;, or use the one already installed on your @@ -23,9 +23,9 @@ system if it is a recent enough version.</para></listitem> Platform. These libraries tended to get combined into a single <literal>kdesupport</literal> module.</para> -<note><para>As of &kde; Platform 4.6, many of the libraries in the kdesupport -module are being migrated over to <ulink -url="http://projects.kde.org/">git.kde.org</ulink>, although they are still not +<note><para>As of &kde; Platform 4.6, many of the libraries in the kdesupport <!--FIXME this is outdated ->frameworks, workspace/Plasma, applications--> +module are being migrated over to the <ulink +url=" https://commits.kde.org/">&kde; git archive</ulink>, although they are still not considered part of the Platform.</para></note> </listitem> @@ -65,8 +65,8 @@ full desktop environment is not provided by the Platform however. modules are known as <quote>Extragear</quote>, and have module names such as <literal>extragear/network</literal>. As with <literal>kdesupport</literal>, some of these Extragear applications are - migrating to <ulink - url="http://projects.kde.org/">git.kde.org</ulink>.</para></listitem> + migrating to the <ulink + url=" https://commits.kde.org/">&kde; git archive</ulink>.</para></listitem> </itemizedlist> </listitem> </orderedlist> @@ -170,7 +170,7 @@ give module-sets a name (as shown in the example), which allows you to quickly refer to the entire group of modules from the command line.</para> <note><para>Module sets are used in supporting module downloads from -the &kde; <ulink url="https://projects.kde.org/">projects.kde.org</ulink> +the &kde; <ulink url="https://commits.kde.org/">&kde; git archive</ulink> module database. See also <xref linkend="kde-projects-module-sets"/>. </para></note> @@ -212,7 +212,7 @@ appropriately. Among other things, &kdesrc-build; will:</para> <itemizedlist> <listitem><para>Download the latest module database from <ulink -url="https://projects.kde.org/">projects.kde.org</ulink>.</para></listitem> +url=" https://commits.kde.org/">&kde; git archive</ulink>.</para></listitem> <listitem><para>Try to find a module with the name given in the module set's <option>use-modules</option> setting.</para></listitem> diff --git a/doc/index.docbook b/doc/index.docbook index e65ab3c7..2a618664 100644 --- a/doc/index.docbook +++ b/doc/index.docbook @@ -144,7 +144,7 @@ <legalnotice>&FDLNotice;</legalnotice> <date>2016-05-02</date> -<releaseinfo>16.05</releaseinfo> +<releaseinfo>&kdesrc-build; 16.05</releaseinfo> <abstract> <para>&kdesrc-build; is a script which builds and installs &kde; software diff --git a/doc/kde-cmake/kde-cmake-intro.docbook b/doc/kde-cmake/kde-cmake-intro.docbook index 0750a8d3..db778464 100644 --- a/doc/kde-cmake/kde-cmake-intro.docbook +++ b/doc/kde-cmake/kde-cmake-intro.docbook @@ -6,7 +6,7 @@ beat out several competitors and was selected to be the build system for &kde; 4 autotools-based system that &kde; has used from the beginning.</para> <para>A introduction to &cmake; page is available on the <ulink -url="http://techbase.kde.org/Development/Tutorials/CMake">&kde; TechBase</ulink>. +url="https://community.kde.org/Guidelines_HOWTOs/CMake">&kde; Community Wiki</ulink>. Basically, instead of running <userinput><command>make</command> <option>-f</option> <filename>Makefile.cvs</filename></userinput>, then <command>configure</command>, then &make;, we simply run &cmake; and then &make;. diff --git a/doc/kdesrc-buildrc/conf-options-table.docbook b/doc/kdesrc-buildrc/conf-options-table.docbook index e1980d8d..66c293e9 100644 --- a/doc/kdesrc-buildrc/conf-options-table.docbook +++ b/doc/kdesrc-buildrc/conf-options-table.docbook @@ -641,7 +641,7 @@ language.</para> <para>To use this option, set it to a space-separated list of languages to install. Each language has a language code associated with it, which you can look up at this page: <ulink -url="http://i18n.kde.org/teams/">http://i18n.kde.org/teams/</ulink>. +url="http://l10n.kde.org/teams-list.php">http://l10n.kde.org/teams-list.php</ulink>. </para> <para>It is alright to choose only one language. By default, none are @@ -1000,8 +1000,8 @@ anonymous repository.</para></note> <entry><para>Use this option to download a specific release of a module.</para> <para><emphasis>Note:</emphasis> The odds are very good that you <emphasis>do not want</emphasis> to use this option. &kde; releases are available in tarball form -from <ulink url="ftp://ftp.kde.org/">The &kde; FTP site</ulink> or one of <ulink -url="http://download.kde.org/download.php">its mirrors</ulink>.</para> +from the <ulink +url="http://download.kde.org/">&kde; download site</ulink>.</para> <note><para>This option has only been supported for git-based modules since &kdesrc-build; 1.16.</para></note> diff --git a/doc/using-kdesrc-build/advanced-features.docbook b/doc/using-kdesrc-build/advanced-features.docbook index 00f0d335..eddc7e3b 100644 --- a/doc/using-kdesrc-build/advanced-features.docbook +++ b/doc/using-kdesrc-build/advanced-features.docbook @@ -21,7 +21,7 @@ option for a module, which will specify a list of directories to download. <tip><para> If you do not already know what to download from a module, it may be a good idea to browse the &subversion; layout for a module first, using -<ulink url="http://websvn.kde.org/branches/KDE/4.6/">WebSVN</ulink>. +<ulink url="http://websvn.kde.org/branches/KDE/4.6/">WebSVN</ulink>. <!--FIXME outdated--> </para></tip> <informalexample> diff --git a/doc/using-kdesrc-build/basic-features.docbook b/doc/using-kdesrc-build/basic-features.docbook index a7f20483..efb8822b 100644 --- a/doc/using-kdesrc-build/basic-features.docbook +++ b/doc/using-kdesrc-build/basic-features.docbook @@ -9,7 +9,7 @@ qt.</para> <note><para>&Qt; is developed under a separate repository from &kde; software located at <ulink -url="http://qt.gitorious.org/qt">http://qt.gitorious.org/qt</ulink>.</para></note> +url="http://code.qt.io/cgit/qt/">http://code.qt.io/cgit/qt/</ulink>.</para></note> <para>In order to build &Qt;, you should make sure that the <link linkend="conf-qtdir">qtdir</link> setting is set to the directory you'd