| Newsgroups |
gmane.linux.lfs.beyond.devel,gmane.linux.lfs.devel |
| Message-ID |
<[email protected]> |
On Sunday, December 8th, 2024 at 07:14, William Harrington <[email protected]> wrote:
>
> snip ... snip ... snip
>
> For a device that somone would wish to use for an LFS host to build LFS I'd
> suggest the following:
>
> Within the ISO, include the following:
>
> The BOOK.
> Number 1: The thing is to include the book. Without the book it
> is useless. May as well use another host distro livecd
>
Just in case it gets someone thinking, with a nod to a Live-CD
needing to combine packages from BLFS along with LFS, some time
ago now, I had coddled together a way to create a Book combining
the LFS and BLFS source trees and having extra chapters for the
stuff I wanted on my system, all in the one "LFS Book".
The fix-up of the XML cross-ref tags was the hardest part but
it can be done.
Maybe the Book on a Live-CD could contain extra chapters for
the extra packages needed to build the Live CD itself.
Sadly, as I am rubbish at keeping an online presence, I don't
have a copy of that rendering (based on a 10.0 Multilib, so
pre-dating the re-working of the UEFI hint into BLFS) up and
visible anywhere at present, so here's the text of the
introduction to the "extra BLFS bits":
In this chapter, and in the following chapters, we add in packages
from the BLFS book that we know we will want on the system. We may
also add in some packages not currently found within the BLFS book
but which are required for extra functionality, for example, in order
to make our LFS system capable of manipulating the UFEI on a machine,
or so as to make out LFS system a Xen Dom0.
For packages that are not found within the current BLFS book, we will
have created a minimal XML section file that allows us to present the
commands required, although at this time much of the typical LFS/BLFS
meta-information about a package may be missing.
12.1.1. Adding BLFS, and locally created, content into the LFS Book sources.
It has been found to be possible to use the BLFS book's XML source files
without too many changes if the files are laid out in the way described
below, assuimng that the Chapter 12 and later directories are at the same
level as their LFS equivalents, vis:
$ find chapter12 -type d
chapter12
chapter12/blfs-packages
chapter12/blfs-packages/xincludes
chapter12/blfs-packages/blfs
chapter12/blfs-packages/blfs/packages
$
$ ls chapter12/
blfs-packages/ chapter12.xml extra-intro.xml
$
$ ls chapter12/blfs-packages/
blfs/ general.ent gnome.ent packages.ent xincludes/
$
$ ls chapter12/blfs-packages/blfs/
packages/
$
$ ls chapter12/blfs-packages/blfs/packages/
bootscripts.xml gpm.xml libaio.xml links.xml lvm2.xml mdadm.xml which.xml
$
$ ls chapter12/blfs-packages/xincludes/
gtk-doc-rebuild-problem.xml static-libraries.xml use-unzip.xml
$
$
$ ls chapter13
chapter13.xml efibootmgr.xml efivar.xml grub.xml intro.xml unifont.xml
$
$ ls chapter14
acpica.xml chapter14.ent chapter14.xml intro.xml ocaml.xml xen.xml yajl.xml
$
The rationale for the layout as shown is that the directory blfs-packages,
within each chapter, serves as the top-level within which the original XML
sources are placed, with the three common "book-level" files general.ent,
gnome.ent, and packages.ent and the three "xinclude" files, gtk-doc-rebuild-problem.xml,
static-libraries.xml, and use-unzip.xml that contain the targets of references
made within the BLFS book then able to be placed as though we were rendering
the BLFS book.
Note that non-BLFS package source content, that has been created explicity
for the extra chapters, get placed at the top level of each of the new chapters.
HTH, or at least provides some food for thought,
Kevin
--
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page