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
This commit is contained in:
Gerard Beekmans 2001-06-28 20:17:36 +00:00
parent bf0b67e6ef
commit 446dd24212

View File

@ -27,20 +27,6 @@ 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>
<para>
The lfscommands can be downloaded from <ulink
url="http://packages.linuxfromscratch.org/lfs-commands/">