Changeset 71df408 for x/installing/installing.xml

Timestamp:

03/21/2020 11:02:56 AM (4 years ago)

Author:

Pierre Labastie <pieere@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

baac59c

Parents:

bdfc854

Message:

Format the x/installing chapter

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@22865 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• x/installing/installing.xml (modified) (1 diff)

x/installing/installing.xml

@@ -16 +16 @@
   <title>X Window System Environment</title>
 
-  <para>This chapter contains instructions to build and configure a graphical
-  user environment.</para>
+  <para>
+    This chapter contains instructions to build and configure a graphical
+    user environment.
+  </para>
 
-  <para><application>Xorg</application>, in addition to clearing up some
-  licensing issues with <ulink url="http://www.xfree86.org/">XFree86</ulink>,
-  introduced a completely auto-tooled build for the X Window system. This
-  means that the packages build and install using the conventional
-  <command>configure</command>, <command>make</command>, and <command>make
-  install</command> commands, as opposed to a proprietary build system that
-  required hand editing of configuration parameters in a C-like syntax.</para>
+  <para>
+    <application>Xorg</application>, in addition to clearing up some
+    licensing issues with <ulink url="http://www.xfree86.org/">XFree86</ulink>,
+    introduced a completely auto-tooled build for the X Window system. This
+    means that the packages build and install using the conventional
+    <command>configure</command>, <command>make</command>, and <command>make
+    install</command> commands, as opposed to a proprietary build system that
+    required hand editing of configuration parameters in a C-like syntax.
+  </para>
 
-  <para><application>Xorg</application> also brought with it a modular build
-  system. While this separation into modules resulted in full control of the
-  features available to the X server on any given installation, it also made
-  the installation more tedious as it requires installing more than 100
-  different packages to obtain a functional X Window environment. Most large
-  commercial distributions have elected to use <application>Xorg</application>
-  over the <application>XFree86</application> distribution due to both
-  licensing issues and the increased functionality provided by it over
-  <application>XFree86</application>. With the modular build system, also came
-  incremental updates to individual packages. The distribution of
-  <application>Xorg</application> is given a release number by the developers,
-  in this case Xorg-&xorg-version;, and is referred to as the "katamari" by
-  the upstream developers.</para>
+  <para>
+    <application>Xorg</application> also brought with it a modular build
+    system. While this separation into modules resulted in full control of the
+    features available to the X server on any given installation, it also made
+    the installation more tedious as it requires installing more than 100
+    different packages to obtain a functional X Window environment. Most large
+    commercial distributions have elected to use <application>Xorg</application>
+    over the <application>XFree86</application> distribution due to both
+    licensing issues and the increased functionality provided by it over
+    <application>XFree86</application>. With the modular build system, also came
+    incremental updates to individual packages. The distribution of
+    <application>Xorg</application> is given a release number by the developers,
+    in this case Xorg-&xorg-version;, and is referred to as the "katamari" by
+    the upstream developers.
+  </para>
 
   <!--
-  <para>Additionally, the BLFS book appends a build number
-  to the end of version string to indicate whether a group of incremental
-  updates has been applied, while still retaining the versioning scheme of the
-  upstream developers. For instance, Xorg-&xorg-version;-1 would indicate that
-  this is the 1st release, and is consistent with the katamari, while
-  Xorg-&xorg-version;-2 would indicate that individual package updates have
-  been applied to the katamari.</para>
+  <para>
+    Additionally, the BLFS book appends a build number
+    to the end of version string to indicate whether a group of incremental
+    updates has been applied, while still retaining the versioning scheme of the
+    upstream developers. For instance, Xorg-&xorg-version;-1 would indicate that
+    this is the 1st release, and is consistent with the katamari, while
+    Xorg-&xorg-version;-2 would indicate that individual package updates have
+    been applied to the katamari.
+  </para>
   -->