diff options
| author | Gerard Beekmans <gerard@linuxfromscratch.org> | 2001-06-28 20:17:36 +0000 |
|---|---|---|
| committer | Gerard Beekmans <gerard@linuxfromscratch.org> | 2001-06-28 20:17:36 +0000 |
| commit | 446dd2421249b1e5c6e376c9c5faf2c2a506f23d (patch) | |
| tree | 8257077796b1d0c523edfd51b3b5b4a3bad7affd | |
| parent | bf0b67e6ef51d7be3f4ce4ad1278aa2f490444c7 (diff) | |
Removed the warning not to put the files inside the source directory.
With the new naming scheme there's no interference anymore
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@727 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
| -rw-r--r-- | chapter02/commands.xml | 14 |
1 files changed, 0 insertions, 14 deletions
diff --git a/chapter02/commands.xml b/chapter02/commands.xml index b1d9ac3a9..99863b584 100644 --- a/chapter02/commands.xml +++ b/chapter02/commands.xml @@ -28,20 +28,6 @@ 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> - -<para> The lfscommands can be downloaded from <ulink url="http://packages.linuxfromscratch.org/lfs-commands/"> http://packages.linuxfromscratch.org/lfs-commands/</ulink> or <ulink |