On Sun, Nov 26, 2006 at 09:25:18AM -0500, Chris Staub wrote: > Nicolas FRANCOIS wrote: > >The instructions are allways refering to this extra material being placed > >in the /sources directory (or whatever directory you use to build your > >packages). Couldn't it be more practical to refer to a $BLFS_PACKAGES > >variable, to permit everyone to put it wherever they want ? A variable > >that should be initialized at the beginning of the books, just like $LFS > >or $XORG_PREFIX or others... > > > >Isn't this a good idea ? > > No, it's not - it is completely unnecessary. $LFS/sources is only > mentioned once in LFS (well, ok, twice...), and even then it's really > just a suggestion - the source directory could be anywhere and called > anything you like, and no package instructions in either LFS or BLFS > refer to any source dir specifically anyway.
What about this (just one example among others). This command can be found from the SVN LFS book in one of the GCC sections: patch -Np1 -i ../gcc-4.1.1-specs-1.patch This command is to be executed in the gcc-4.1.1 directory and the command works if, and only if, the patch file is in the directory just above this gcc-4.1.1 directory. I never have built an LFS system, where I could have used this command as it is in the book. IMHO all commands that often need modification, should be marked as such, eg. patch -Np1 -i [your source directory]/gcc-4.1.1-specs-1.patch The LFS layout, where all patches are in ../ is not very practical, since in directory listing source directories get buried under the names of package and patch files. It also makes it impossible to delete the gcc tree like this: # rm -rf gcc-* -- Tapio -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
