Changeset 0d7900a for introduction/important

Timestamp:

02/11/2013 06:51:17 PM (11 years ago)

Author:

Randy McMurchy <randy@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

8f83eeb

Parents:

a161de9

Message:

Removed extraneous spaces from blank lines and at the end of lines in the .xml

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

Location:

introduction/important

Files:

• libraries.xml (modified) (5 diffs)
• locale-issues.xml (modified) (1 diff)

introduction/important/libraries.xml

@@ -29 +29 @@
     systems they are the only type available.</para>
 
-    <para>On almost all Linux platforms there are also shared libraries 
-    (libfoo.so) - one copy of the library is loaded into virtual memory, and 
-    shared by all the programs which call any of its functions. This is space 
+    <para>On almost all Linux platforms there are also shared libraries
+    (libfoo.so) - one copy of the library is loaded into virtual memory, and
+    shared by all the programs which call any of its functions. This is space
     efficient.</para>
 
@@ -55 +55 @@
     program is (re)started (provided the library major version is unchanged,
     e.g. going from libfoo.so.2.0 to libfoo.so.2.1. Going to libfoo.so.3
-    will require recompilation - <command>ldd</command> can be used to find 
-    which programs use the old version). If a program is linked to a static 
-    library, the program always has to be recompiled. If you know which 
-    programs are linked to a particular static library, this is merely an 
-    annoyance. But usually you will <emphasis>not</emphasis> know which 
+    will require recompilation - <command>ldd</command> can be used to find
+    which programs use the old version). If a program is linked to a static
+    library, the program always has to be recompiled. If you know which
+    programs are linked to a particular static library, this is merely an
+    annoyance. But usually you will <emphasis>not</emphasis> know which
     programs to recompile.</para>
 
@@ -65 +65 @@
     moving a shared library to <filename class="directory">/lib</filename>
     accidentally breaking the <literal>.so</literal> symlink in
-    <filename class="directory">/usr/lib</filename> while keeping the static 
-    library in <filename class="directory">/lib</filename>, the static library 
+    <filename class="directory">/usr/lib</filename> while keeping the static
+    library in <filename class="directory">/lib</filename>, the static library
     will be silently linked into the programs which need it.</para>
 
@@ -72 +72 @@
     at the end of the installation of every package.  Write a script to find all
     the static libraries in <filename class="directory">/usr/lib</filename> or
-    wherever you are installing to, and either move them to another directory so 
-    that they are no longer found by the linker, or rename them so that libfoo.a 
-    becomes e.g. libfoo.a.hidden. The static library can then be temporarily 
-    restored if it is ever needed, and the package needing it can be 
-    identified. You may choose to exclude some of the static libraries from 
+    wherever you are installing to, and either move them to another directory so
+    that they are no longer found by the linker, or rename them so that libfoo.a
+    becomes e.g. libfoo.a.hidden. The static library can then be temporarily
+    restored if it is ever needed, and the package needing it can be
+    identified. You may choose to exclude some of the static libraries from
     glibc if you do this (<filename>libc_nonshared.a, libg.a, libieee.a, libm.a,
-    libpthread_nonshared.a, librpcsvc.a, libsupc++.a</filename>) to simplify 
+    libpthread_nonshared.a, librpcsvc.a, libsupc++.a</filename>) to simplify
     compilation.</para>
 
 <!-- versions hardcoded in this para, it's a comment on those versions  -->
-    <para>If you use this approach, you may discover that more packages than 
+    <para>If you use this approach, you may discover that more packages than
     you were expecting use a static library. That was the case with
-    <application>nettle-2.4</application> in its default static-only 
+    <application>nettle-2.4</application> in its default static-only
     configuration: It was required by <application>GnuTLS-3.0.19</application>,
-    but also linked into package(s) which used 
-    <application>GnuTLS</application>, such as 
+    but also linked into package(s) which used
+    <application>GnuTLS</application>, such as
     <application>glib-networking-2.32.3</application>.</para>
 
     <para>Many packages put some of their common functions into a static
     library which is only used by the programs within the package and,
-    crucially, the library is <emphasis>not</emphasis> installed as a 
-    standalone library. These internal libraries are not a problem - if the 
-    package has to be rebuilt to fix a bug or vulnerability, nothing else is 
+    crucially, the library is <emphasis>not</emphasis> installed as a
+    standalone library. These internal libraries are not a problem - if the
+    package has to be rebuilt to fix a bug or vulnerability, nothing else is
     linked to them.</para>
 
-    <para>When BLFS mentions system libraries, it means shared versions of 
-    libraries. Some packages such as <xref linkend="firefox"/> and 
-    <xref linkend="gs"/> include many other libraries. When they link to them, 
-    they link statically so this also makes the programs bigger. The version 
-    they ship is often older than the version used in the system, so it may 
-    contain bugs - sometimes developers go to the trouble of fixing bugs in 
+    <para>When BLFS mentions system libraries, it means shared versions of
+    libraries. Some packages such as <xref linkend="firefox"/> and
+    <xref linkend="gs"/> include many other libraries. When they link to them,
+    they link statically so this also makes the programs bigger. The version
+    they ship is often older than the version used in the system, so it may
+    contain bugs - sometimes developers go to the trouble of fixing bugs in
     their included libraries, other times they do not.</para>
 
@@ -109 +109 @@
     <xref linkend="libpng"/> if used for <xref linkend="firefox"/>).
     Occasionally, a package ships an old library and can no longer link to
-    the current version, but can link to an older version. In this case, BLFS 
-    will usually just use the shipped version. Sometimes the included library 
-    is no longer developed separately, or its upstream is now the same as the 
-    package&apos;s upstream and you have no other packages which will use it. 
+    the current version, but can link to an older version. In this case, BLFS
+    will usually just use the shipped version. Sometimes the included library
+    is no longer developed separately, or its upstream is now the same as the
+    package&apos;s upstream and you have no other packages which will use it.
     In those cases, you might decide to use the included static library even if
     you usually prefer to use system libraries.</para>

introduction/important/locale-issues.xml

@@ -113 +113 @@
     this causes problems with UTF-8 encoded TeX documents created in
     Linux. On Windows, most applications will assume that these documents
-    have been created using the default Windows 8-bit encoding. 
+    have been created using the default Windows 8-bit encoding.
     </para>