Changeset fec335e

Timestamp:

05/08/2001 08:36:29 PM (23 years ago)

Author:

Gerard Beekmans <gerard@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

7f001c1

Parents:

51542c7

Message:

• Updated what the files are for
• Mentioned that you shouldn't copy the lfs-command files inside a package directory + gave an example what happens with autoconf when you do so

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@597 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter02/commands.xml (modified) (1 diff)

chapter02/commands.xml

@@ -4 +4 @@
 <para>
 LFS Commands is a tarball containing files which list the installation
-commands for the packages installed in this book. These files can be
-used to dump to a shell and install the packages, though some files 
-need to be modified (for example, when the kbd package is 
-installed, you needed to select the keyboard layout file, becaue it can't 
-reliably be guessed).
+commands for the packages installed in this book.
 </para>
 
 <para>
-These files can also be used to quickly find out which commands have been
-changed between the different LFS versions as well. Download the
-lfs-commands tarball for this book version and the previous book version 
-and run a diff on the files. That way it is possible to see which packages
-have updated installation instructions, so any scripts you may have can 
-be modified, or you can reinstall a package if you think that
+These files can also be used to quickly find out which commands have
+been changed between the different LFS versions as well. Download the
+lfs-commands tarball for this book version and the previous book
+version and run a diff on the files. That way it is possible to see which
+packages have updated installation instructions, so any scripts you may 
+have can be modified, or you can reinstall a package if you think that
 necessary.
+</para>
+
+<para>
+A side effect is that these files can be used to dump to a shell and 
+install the packages, though some files need to be modified (for 
+example, when the kbd package is installed, you needed to select the 
+keyboard layout file, becaue it can't reliably be guessed). Keep in
+mind, please, that these files are not checked for correctness,
+integrity and so forth. There may be bugs in the files (since they are
+manually created, typo's are often inevitable) so do check them and
+don't blindly trust them.
+</para>
+
+<para>
+If you decide to use these files for scripting purposes, then don't 
+place the files inside the directory of a package. For example, don't 
+put the autoconf file from the lfs-commands package into the autoconf
+directory. The files may interfere with the actual package files, which
+may contain a file with the same name. Autoconf is one
+example of this: if an autoconf file is present in the autoconf
+directory, the configure script won't create a new autoconf file. You 
+will end up with /usr/bin/autoconf containing autoconf's installation 
+instructions, rather than the real autoconf perl script. There may be
+other packages that behave in similar ways, so just keep the
+lfs-commands files outside the package directory.
 </para>