additions to the README file
This commit is contained in:
parent
93135fd151
commit
511923a97f
2 changed files with 25 additions and 2 deletions
22
README
22
README
|
@ -76,6 +76,22 @@ $Id$
|
||||||
Q. "It doesn't work"
|
Q. "It doesn't work"
|
||||||
A. Yes it does..
|
A. Yes it does..
|
||||||
|
|
||||||
|
Q. "How do I specify the build location"
|
||||||
|
A. The original LFS document worked against the well know location /mnt/lfs.
|
||||||
|
This script automates the build of all of the LFS series of books and uses
|
||||||
|
a default generic location $BUILDDIR. The default setting is /mnt/build_dir.
|
||||||
|
You may change this value to suit your needs.
|
||||||
|
|
||||||
|
The layout below $BUILDDIR is as follows.
|
||||||
|
$BUILDDIR/
|
||||||
|
jhalfs (makefile,cmd scripts,logs..etc)
|
||||||
|
sources (where packages reside
|
||||||
|
temptools (temporary bootstrap system
|
||||||
|
cross-tools (CLFS only)
|
||||||
|
...
|
||||||
|
FHS dir structure
|
||||||
|
...
|
||||||
|
|
||||||
Q. "What is the function of the SRC_ARCHIVE variable
|
Q. "What is the function of the SRC_ARCHIVE variable
|
||||||
A. When then symlinked master.sh runs it creates a local copy of the
|
A. When then symlinked master.sh runs it creates a local copy of the
|
||||||
necessary packages in BUILDDIR/sources by downloading the files. If
|
necessary packages in BUILDDIR/sources by downloading the files. If
|
||||||
|
@ -84,6 +100,12 @@ $Id$
|
||||||
If the files are not found in SRC_ARCHIVE _and_ you have write priv to
|
If the files are not found in SRC_ARCHIVE _and_ you have write priv to
|
||||||
the directory any downloaded files will be mirrored there.
|
the directory any downloaded files will be mirrored there.
|
||||||
|
|
||||||
|
Q. "How do I set the SRC_ARCHIVE location"
|
||||||
|
A. The best way to set the value of SRC_ARCHIVE is
|
||||||
|
export SRC_ARCHIVE=/wherever/you/store/downloaded/packages
|
||||||
|
OR
|
||||||
|
you can change the setting in .common/config.
|
||||||
|
|
||||||
Q. "Why have 2 copies of the files."
|
Q. "Why have 2 copies of the files."
|
||||||
A. The package files must be visible during the chroot phase and this is a
|
A. The package files must be visible during the chroot phase and this is a
|
||||||
simple and reliable method of doing so. This method also handles the CLFS
|
simple and reliable method of doing so. This method also handles the CLFS
|
||||||
|
|
|
@ -53,6 +53,7 @@ ${BOLD} -B, --book VER${OFF}
|
||||||
${BOLD} -D --directory DIR${OFF}
|
${BOLD} -D --directory DIR${OFF}
|
||||||
use DIR directory for building ${BOLD}$(echo $PROGNAME | tr [a-z] [A-Z])${OFF}; all files jhalfs produces
|
use DIR directory for building ${BOLD}$(echo $PROGNAME | tr [a-z] [A-Z])${OFF}; all files jhalfs produces
|
||||||
will be in the directory DIR/jhalfs.
|
will be in the directory DIR/jhalfs.
|
||||||
|
The current setting for BUILDDIR is "$BUILDDIR"
|
||||||
|
|
||||||
${BOLD} -G, --get-packages${OFF}
|
${BOLD} -G, --get-packages${OFF}
|
||||||
download the packages and patches. This assumes that the server declared
|
download the packages and patches. This assumes that the server declared
|
||||||
|
|
Reference in a new issue