Ken Moffat wrote:
On Mon, Dec 01, 2014 at 03:30:04PM +0000, John Burrell wrote:
It would be very nice if these two books had the same packages occupying the
same sections.
For the most part this is the case but I noticed that
Appstream-Glib-0.3.3
is in 'General Utilities' in BLFS-systemd
while
Appstream-Glib-0.3.1
is in 'Libraries' in KBLFS
This may seem trivial but if it's the thin end of a wedge, then you are heading
for chaos.
My script installs BLFS packages section by section and works well if the
packages and sections are consistent in each version of the book. Gets tricky
though if a package starts leaping around!
Trust you all enjoyed 'Black Friday' :-(
jb.
Unless you are intending to install _everything_ from whichever book
you are currently _using_, it sems to me that building section by
section is not a useful approach. For example, mail servers almost
always provide a 'sendmail' command, so only one of them can be used
at a time.
And if you *are* installing everything to test the instructions, I
assume you are working with the xml? Could you, at an early stage
in your process, create a list of the sections, and then for each
section a list of packages with some sort of pointer to where you
will find the commands/dependencies for that package ?
Alternatively, follow one book at a time, and if you change to a
different book then accept that you may need to change parts of your
scripts.
I agree with Ken. There are three versions:
trunk - does not depend on systemd
systemd - has packages that are not in trunk
kblfs - similar to systemd but with additional/alternative packages
The three versions are due to the interests of the specific editors. A
lot of systemd and kblfs entries are copied from trunk (and that is OK),
but I don't think we can make any assumptions about the contents in the
three different versions.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
