Added information regarding book order.

GLFS should be followed right after LFS but before BLFS.
This commit is contained in:
Zeckmathederg 2024-08-02 22:49:04 -06:00
parent 8c9e8b8eb0
commit e124be8f94
5 changed files with 35 additions and 13 deletions

View File

@ -46,11 +46,11 @@
<abstract>
<para>
This book both follows on from and treads back to the Linux From Scratch
book. It follows the same principles as the Beyond Linux From Scratch book
but aims to only suppliment it. It introduces and guides the reader
through additions to the system like <application>Steam</application> and
<application>Wine</application>, and the packages along the way.
This book introduces and guides the reader through additions to the
system like <application>Steam</application>,
<application>Wine</application>, and their dependencies after the LFS
book or the LFS Multilib book on x86_64 systems. This book is meant to be
followed before BLFS.
</para>
</abstract>

View File

@ -12,10 +12,9 @@
<title>Foreword</title>
<para>
This version of the book is meant to be a separate book from LFS
and BLFS entirely but meant to be used in conjuction with BLFS.
This is meant to be built on Thomas' Multilib mirror with
modifications.
This book is separate from LFS and BLFS, where it should be followed after
LFS but before BLFS. On x86_64 systems, this book is meant to be followed
after Thomas' Multilib mirror of LFS.
</para>
<para>
@ -28,7 +27,7 @@
<blockquote>
<literallayout>Zeckma
April 5th, 2024</literallayout>
August 2nd, 2024</literallayout>
</blockquote>
</sect1>

View File

@ -42,6 +42,9 @@
<listitem>
<para>August 2nd, 2024</para>
<itemizedlist>
<listitem>
<para>[Zeckmathederg] - Added information regarding book order.</para>
</listitem>
<listitem>
<para>[Zeckmathederg] - HarfBuzz: Add important tag regarding Glib.</para>
</listitem>

View File

@ -20,6 +20,27 @@
here.
</para>
<sect2>
<title>Book Order</title>
<para>
GLFS can be great if you follow it right after the LFS vanilla or
multilib books; however, it can be a pain to do if you have followed BLFS
after LFS and are now getting around to doing GLFS. One such issue that can
arise from this practice is packages may be detected via
<command>pkgconf</command>, such as Glib, where a 64-bit only install is
detected whilst trying to install a 32-bit package, leading to linker errors.
</para>
<para>
As such, it is recommended that you first follow the
LFS vanilla or multilib books first, then GLFS right after.
<emphasis>THEN</emphasis> you may follow BLFS and
install the packages you are used to using.
</para>
</sect2>
<sect2>
<title>Init System</title>

View File

@ -91,9 +91,8 @@
/usr/lib/pkgconfig/NOUSE.glib-2.0.pc</userinput></screen>
<para>
After you are done installing this package, you may move it back.
Doing this is not supported by the GLFS Development Team. It is
recommended to only install the packages in GLFS first before moving
on to install other packages, notably those that appear in BLFS.
Doing all of this is not recommended. Please read up on
<xref linkend="important"/> for more information.
</para>
</important>