- the problem is when a .dep file contains pack-A pack-B pack-A. If pack-A
and pack-B have some dep in common, say pack-C, that dep is erased from
pack-B, with the idea that it will be built as a dep of pack-A. But when
the program encounters the second pack-A, it removes the first one, so that
pack-C is built before the second pack-A, but after pack-B. Sorting was
a good workaround, but removing the last line instead of the first is
much better.
- Otherwise, add Xfce and Lxde to the list of packages whose preceding
sibling is a required dep.
When the .dep file is scanned during the tree building, it outputs dependencies
in the file order, while when the tree is scanned later, dependencies are
output in alphabetical order. This may eventually lead to a wrong order
at the end. To be sure that both output are the same, just sort
the .dep file before scanning it.
- the tzdata DESTDIR should not be tzdata, because some package managers use
$PACKAGE as their working directory, and this may conflicts with this one.
tzdata DESTDIR is now 001-tzdata
- when reading md5sums, the current code assumes that there is only one
<para><literal> node reachable from ../.. (relative to <ulink>). This is true
for the "official" book, but not necessarily for the snippets written for
package management. The following change only assumes that the md5sum
<para><literal> for a given <ulink> is the first one after <para><ulink>,
which does not change anything for the book, and is better for user
written snippets.
unpacking the booscripts. Then, when we want to remove the build directory
of the package, the UNPACKDIR is set to something else and the build
directory is not removed.
- introduce a template for downloading code
- account for various layout of the BLFS pages for package information and additional
downloads
- Add the possibility for addtional downloads in xorg pages
- add 32 bit critical tests when in multilib
- allow the "note" in perl to be run only when method=boot, and tests
are asked
- remove some useless lines
- Do not put the chroot commands in $PROGNAME-commands, but rather
in a separate directory chroot-scripts
- Use the commands in the chroot-scripts directory to generate the CHROOT
variables in Makefile
- The commands are extracted to $PROGNAME-commands only if they do not
have role="nodump attribute and they do not begin with "chroot" (for
compatibility with previous books where chroot commands did not have
the role="nodump" attribute.
