Tapio Kelloniemi wrote:
On Sun, Nov 26, 2006 at 09:25:18AM -0500, Chris Staub wrote:
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-*
Then unpack your source tarballs wherever you like. I still see no
reason to change what's in the book, as I do have all the source and
patches in one dir and have no problems doing it that way. Besides, why
would you need to use "rm -rf gcc-*" to remove the GCC source and build
dirs? It's not that difficult to add the extra "4.0.3" or "build" to the
dir name (or use bash's tab completion to make it really easy). Don't
forget you could also use "tar tf" to list the files in a tarball, or
"tar xvf" for a verbose listing that tells you exactly what's being
unpacked and what directory it's all going into.
Adding a $SOURCEDIR variable where none is needed is just adding another
level of user hand-holding to the book (and there's already enough as it
is). I do not see any point to changing the instructions.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
