Changeset d7818f5 for README

Timestamp:

02/24/2012 03:29:08 PM (12 years ago)

Author:

Pierre Labastie <pierre@…>

Branches:

ablfs

Children:

5e9076f

Parents:

96a30c7

Message:

Updates to README and README.BLFS. First "alpha release"

File:

• README (modified) (2 diffs)

README

@@ -78 +78 @@
 6. BLFS_TOOL SUPPORT::
 
-     For books that support it, there is an option to install blfs-tool and its
-     dependencies on the final system. The pre-made build dependencies
+     For books that support it (TODO: which ones?), there is an option
+     to install an automated framework for building BLFS packages. Let
+     us call it blfs-tool for now. When you tick `BOOK Settings/Add
+     blfs-tool support' in jhalfs configuration menu, the tools are
+     installed in $BLFS_ROOT (default /blfs_root) on the xLFS system,
+     and a few dependencies (which you may select) are built at the
+     end of the jhalfs run. The pre-made build dependencies
      scripts has been written based on a LFS build. For CLFS and HLFS
-     builds you may need to adjust that scripts, that are found into the
+     builds you may need to adjust those scripts, that are found into the
      common/blfs-tool-deps directory in the jhalfs sources tree.
 
+     (TODO: is this relevant to present CLFS?)
      WARNING:: If you add blfs-tool support on a CLFS Sysroot build
-               you MUST to edit the dependencies scripts to fix the
-               installation paths.
-               Be careful when you modify the scripts as you can
-               easily disable the host system.
+               you MUST edit the scripts to fix the installation paths.
 
      After booting the new xLFS system some steps are needed to finish
-     blfs-tool installation:
+     the installation of the automated tools:
 
        - A user account must be created. You must be logged on that user
-         account to use blfs-tool.
+         account to use blfs-tool. This is not strictly necessary,
+         since the packages can be built as root, too, but it is
+         never a good idea to build packages as root.
 
        - Move /blfs-root to that user's home and change ownership of the
@@ -105 +110 @@
          remove the libxml2 and libxslt trackin files found in $TRACKING_DIR.
 
-       - Configure sudo, adding the needed privileges for the user.
+       - Configure sudo, adding the needed privileges for the user. For
+         newer sudo version, do not forget to add a line Defaults secure_path=
+         containing /sbin and /usr/sbin (in /etc/sudoers), otherwise some
+         executables are not found.
+
+       - Although it is not strictly necessary, it is recommended to install
+         the bash shell startup files (as per `3.After LFS Configuration
+         Issues' of the BLFS book), as some instructions in BLFS rely on
+         their being present.
 
      We assume that blfs-tool will be used on a running fresh xLFS system.
      To use it to build BLFS packages from the chroot jail is also possible,
-     but is for you to figure out how to do that.
-
-     To know how to blfs-tool works, see README.BLFS.
+     but not supported.
+
+     To know how to use blfs-tool, see README.BLFS.
 
 7. LAYOUT::