linux-from-scratch/glfs
1
0
Fork 0
mirror of https://github.com/Zeckmathederg/glfs.git synced 2025-01-23 22:42:14 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Formatted the look to better match LFS as it looks cleaner than BLFS. Also adjusted BLFS-Next and mentions of BLFS not changed as they should have been -> GLFS.

Browse Source
This commit is contained in:
Zeckmathederg 2024-04-28 14:26:29 -06:00
parent 715c6b235f
commit ad97dbd115
10 changed files with 28 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
book/bookinfo.xml
View File

@ -9,10 +9,11 @@
<date>$Date$</date>
<title>Beyond Linux<superscript>&reg;</superscript> From Scratch Next
<phrase revision="systemd">(systemd</phrase>
<phrase revision="sysv">(System V</phrase> Edition)</title>
<title>
Gaming Linux<superscript>&reg;</superscript> From Scratch
</title>
<subtitle>Version &version;</subtitle>
<subtitle>Published &releasedate;</subtitle>
<authorgroup>
<corpauthor>
@ -20,8 +21,6 @@
</corpauthor>
</authorgroup>
<pubdate>Published &pubdate;</pubdate>
<copyright id="copyright">
<year>&copyrightdate;</year>
<holder>&copyholder;</holder>

4
book/organization.xml
View File

@ -50,8 +50,8 @@
<bridgehead renderas="sect2">Part V - Wine</bridgehead>
<para>
This section goes over installing toolchains like Mingw-w64
and gnat, some of the packages necessary to both compile Wine
This section goes over installing toolchains like MinGW-w64
and GNAT, some of the packages necessary to both compile Wine
and use it, and lastly how to compile Wine and configure it.
</para>

10
general.ent
View File

@ -50,12 +50,12 @@
]]><!-- End %release -->
<!ENTITY copyrightdate "1999-&year;">
<!ENTITY copyholder "The BLFS Development Team">
<!ENTITY copyholder "The GLFS Development Team">
<!ENTITY lfs-domainname "linuxfromscratch.org">
<!ENTITY maintainer-fullname "The BLFS Team">
<!ENTITY maintainer-firstname "BLFS">
<!ENTITY maintainer-address "blfs-maintainer@&lfs-domainname;">
<!ENTITY maintainer-fullname "The GLFS Team">
<!ENTITY maintainer-firstname "GLFS">
<!ENTITY maintainer-address "zeckmaisreal@gmail.com;">
<!ENTITY lfs-website "https://www.&lfs-domainname;">
@ -124,7 +124,7 @@
<!-- These entities are used to annotate the current status of a package as it
relates to the version of LFS it will build/work against -->
<!ENTITY lfs121_checked "<note><para>Development versions of BLFS may not build or run
<!ENTITY lfs121_checked "<note><para>Development versions of GLFS may not build or run
some packages properly if LFS or dependencies have been updated
since the most recent stable versions of the books.</para></note>">

2
introduction/welcome/askhelp.xml
View File

@ -24,7 +24,7 @@
For now if your issue should be reported to us, please refer to
<xref linkend="contactinfo"/>
and shoot any of the people listed in the section an email.
Make it clear it's a BLFS-Next issue.
Make it clear it's a GLFS issue.
</para>
</sect1>

12
introduction/welcome/conventions.xml
View File

@ -99,7 +99,7 @@ EOF</userinput></screen>
<title>Conventions Used for Package Dependencies</title>
<para>When new packages are created, the software's authors depend on prior work. In
order to build a package in BLFS, these dependencies must be built before
order to build a package in GLFS, these dependencies must be built before
the desired package can be compiled. For each package, prerequisites are listed
in one or more separate sections: Required, Recommended, and Optional.</para>
@ -114,7 +114,7 @@ EOF</userinput></screen>
<bridgehead renderas="sect3">Recommended Dependencies</bridgehead>
<para>These are dependencies the BLFS editors have determined
<para>These are dependencies the GLFS editors have determined
are important to give the package reasonable capabilities. If a
recommended dependency is not said to be <quote>runtime</quote>, package
installation instructions assume it is installed. If it
@ -128,8 +128,8 @@ EOF</userinput></screen>
<para>These are dependencies the package <emphasis>may</emphasis> use. Integration
of optional dependencies may be automatic by the package, or
additional steps not presented by BLFS may be necessary. Optional dependencies are
sometimes listed without explicit BLFS instructions. In this case you must
additional steps not presented by GLFS may be necessary. Optional dependencies are
sometimes listed without explicit GLFS instructions. In this case you must
determine how to perform the installation yourself.</para>
<para>&nbsp;</para> <!-- add extra white space to improve readability -->
@ -261,9 +261,9 @@ EOF</userinput></screen>
</sect2>
<sect2>
<title>SBU values in BLFS</title>
<title>SBU values in GLFS</title>
<para>As in LFS, each package in BLFS has a build time listed in Standard
<para>As in LFS, each package in GLFS has a build time listed in Standard
Build Units (SBUs). These times are relative to the time it took to build
binutils in LFS, and are intended to provide some insight into how long it
will take to build a package. Most times listed are for a single processor

2
introduction/welcome/credits.xml
View File

@ -12,7 +12,7 @@
<title>Credits</title>
<sect2>
<title>BLFS-Next Current Editors</title>
<title>GLFS Current Editors</title>
<itemizedlist>

2
introduction/welcome/important.xml
View File

@ -25,7 +25,7 @@
<title>Building software</title>
<para>
Building software on BLFS-Next is identical to how it's done in the
Building software on GLFS is identical to how it's done in the
BLFS books, along with having lib32 compilation instructions. It
goes without saying firstmost that you should have <envar>MAKEFLAGS</envar>
set to save yourself a lot of time. This is useful for the <command>make

6
introduction/welcome/packages.xml
View File

@ -11,7 +11,7 @@
<title>Getting the Source Packages</title>
<para>Within the BLFS-Next instructions, each package has two references for
<para>Within the GLFS instructions, each package has two references for
finding the source files for the package&mdash;an HTTP link and an FTP link
(some packages may only list one of these links). Every effort has been made
to ensure that these links are accurate. However, the World Wide Web is in
@ -24,7 +24,7 @@
url="https://www.linuxfromscratch.org/blfs/download.html#sources">
https://www.linuxfromscratch.org/blfs/download.html#sources</ulink> for a
list. These sites have all the sources of the exact versions of the packages
used in BLFS. If you can't find the BLFS or BLFS-Next package you need at the
used in BLFS. If you can't find the BLFS or GLFS package you need at the
listed addresses, get it from these sites.</para>
<para>We would like to ask a favor, however. Although this is a public
@ -36,7 +36,7 @@
is the site or sites set up by the source code developer. Please try
there first.</para>
<para>As for BLFS-Next, some packages listed here are not on BLFS or their site.
<para>As for GLFS, some packages listed here are not on BLFS or their site.
In such a case, we do not have a solution at the moment besides going to the
developer(s) and/or their website.</para>

4
introduction/welcome/welcome.xml
View File

@ -8,10 +8,10 @@
<chapter id="welcome">
<?dbhtml filename="welcome.html"?>
<title>Welcome to BLFS-Next</title>
<title>Welcome to GLFS</title>
<para>
The BLFS-Next book is designed to be taken in optional chunks
The GLFS book is designed to be taken in optional chunks
and cover most setups users might be using. It is different
from both LFS and BLFS in that LFS is meant to be followed
almost command by command unless otherwise told so, and BLFS

6
introduction/welcome/which.xml
View File

@ -12,7 +12,7 @@
<title>Which Sections of the Book Do I Want?</title>
<para>
BLFS-Next stands as a format in between LFS and BLFS so this
GLFS stands as a format in between LFS and BLFS so this
part is crucial to understanding what you need to read and/or
follow in order to get out of the system that you desire.
For starters, LFS is meant to be followed in a linear manner,
@ -23,7 +23,7 @@
</para>
<para>
As previously mentioned, BLFS-Next stands as a format in
As previously mentioned, GLFS stands as a format in
between the two books. Not every chapter will be necessary
but depending on what the user wants will have to read
everything in the relevant chapter depending on if they
@ -77,7 +77,7 @@
</para>
<para>
We hope you enjoy using BLFS-Next. May you realize that LFS can
We hope you enjoy using GLFS. May you realize that LFS can
compete with just-works distros and even minimalist ones, instead
of seeming like it's stuck in the past!
</para>