From 446dd2421249b1e5c6e376c9c5faf2c2a506f23d Mon Sep 17 00:00:00 2001 From: Gerard Beekmans Date: Thu, 28 Jun 2001 20:17:36 +0000 Subject: 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 --- chapter02/commands.xml | 14 -------------- 1 file changed, 14 deletions(-) (limited to 'chapter02') diff --git a/chapter02/commands.xml b/chapter02/commands.xml index b1d9ac3a9..99863b584 100644 --- a/chapter02/commands.xml +++ b/chapter02/commands.xml @@ -27,20 +27,6 @@ manually created, typo's are often inevitable) so do check them and don't blindly trust them. - -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. - - The lfscommands can be downloaded from -- cgit v1.2.3-54-g00ecf