Please bear with me here, I think this makes (some) sense.
I started this with the 7.7 books but then got waylaid by the
GMP issue I discovered and then never got back to it but have
now come to revisit it with the recently announced 7.8.
I am aware, from the history of LFS, that the order in which
the packages get installed is really well thought out, although
there have been a small set of packages that are not really
constrained by dependency or other concerns and which were
left in alphabetical order
Because of what I was/am trying to do, I had reason to dump
the text of the LFS nochunks books for both the "standard"
book and the "systemd" book and do a diff on them.
If you are interested try
lynx -nolist -dump LFS-BOOK-7.8-NOCHUNKS.html > \
LFS-BOOK-7.8-NOCHUNKS.txt
and similarly for the systemd book and then a "diff -bwy"
First up, I wanted to say, just in case I am the only person
ever to have done this, just how amazingly close to each other
these two strands of LFS are, when viewed in this way.
It really does say a lot about the work that has gone into
LFS over the years in making it as pared down as possible.
(Ok, there a few mismatches where the SBUs are out by a 0.01
and/or where the installed size is out by 1, but that's
not really the point)
Secondly, and my reason for writing here, is the observation that,
when viewing the package order differences apparent from the TOC,
the first differences, that get applied to the package order,
manifest themsleves as follows, right at the end of Chapter 6, so
a long, long way in the overall build:
o Patch-2.7.5 o Patch-2.7.5
o Sysklogd-1.5.1 | o Systemd-224
o Sysvinit-2.88dsf | o D-Bus-1.8.20
o Tar-1.28 <
o Texinfo-6.0 <
o Eudev-3.1.2 <
o Util-linux-2.27 o Util-linux-2.27
o Man-DB-2.7.2 o Man-DB-2.7.2
> o Tar-1.28
> o Texinfo-6.0
o Vim-7.4 o Vim-7.4
o About Debugging Symbols o About Debugging Symbols
o Stripping Again o Stripping Again
o Cleaning Up o Cleaning Up
+ 7. System Configuration and Bootscripts | + 7. Basic System Configuration
Thirdly, and what I'd like to suggest, is to ask whether Tar and Texinfo
need to come before Eudev, or indeed if Vim and Man-DB have a similar need
to be where they are.
For example, I could imagine even less difference in the ordering, by moving
Tar and Texinfo above the "init" switch, as follows
o Patch-2.7.5 o Patch-2.7.5
o Sysklogd-1.5.1 | o Systemd-224
o Sysvinit-2.88dsf | o D-Bus-1.8.20
o Tar-1.28 o Tar-1.28
o Texinfo-6.0 o Texinfo-6.0
o Eudev-3.1.2 <
o Util-linux-2.27 o Util-linux-2.27
o Man-DB-2.7.2 o Man-DB-2.7.2
o Vim-7.4 o Vim-7.4
o About Debugging Symbols o About Debugging Symbols
o Stripping Again o Stripping Again
o Cleaning Up o Cleaning Up
+ 7. System Configuration and Bootscripts | + 7. Basic System Configuration
or even (and here I'm assuming Util-linux needs to come in after the "init"
choice has been made, and certainly after Eudev in the "standard" book), by
moving all four of Tar, Texinfo, Man-DB and Vim above it.
o Patch-2.7.5 o Patch-2.7.5
o Tar-1.28 o Tar-1.28
o Texinfo-6.0 o Texinfo-6.0
o Man-DB-2.7.2 o Man-DB-2.7.2
o Vim-7.4 o Vim-7.4
o Sysklogd-1.5.1 | o Systemd-224
o Sysvinit-2.88dsf | o D-Bus-1.8.20
o Eudev-3.1.2 <
o Util-linux-2.27 o Util-linux-2.27
o About Debugging Symbols o About Debugging Symbols
o Stripping Again o Stripping Again
o Cleaning Up o Cleaning Up
+ 7. System Configuration and Bootscripts | + 7. Basic System Configuration
What this would mean, in the way I was looking to do things, was that
one could build a even larger portion of a generic proto-LFS, before having
to start building the two or three packages specific to the Sysvinit or
systemd strands.
Just a suggestion though,
Kevin
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
