Started support to customize de base system build allowing Makefile regeneration.

Config.in

@@ -823,3 +823,16 @@ endif
 
 #--- End Advanced Features
 endmenu
+
+config RE_MAKE
+	bool "Rebuild the Makefile (see help)"
+	default n
+	depends on !BOOK_BLFS
+	help
+		#-- Rebuild the Makefile
+		#
+		#   This option alow to rebuild the Makefile after
+		#   customizing the base system build scripts.
+		#
+		#   See README.CUSTOM for more info about this feature.
+

README.CUSTOM

@@ -10,6 +10,39 @@ needs of every individual and requests are made "Can you add xxxx package".
 Rather than adding numerous package scripts and switches for each request it
 was easier to add a tool for the user(s) to code their own package needs.
 
+  There is two areas that can be customized: how the base system is build
+and what additional configurations and packages requires your hardware to can
+boot and work with. Each one of this areas is handled in a diferent way.
+
+        BASE SYSTEM CUSTOMIZATION
+
+  There is two ways to alter how the base system will be built:
+
+  - Using a working copy of the book sources and editing the XML files.
+    This is the way used by book editors to test packages upgrades,
+    command changes, build order changes. etc.
+
+    This method requires you know very well the book sources and what
+    files need be edited. It will not be discussed here.
+
+  - Editing the generated build scripts to make any change you would.
+    This is the method discussed below.
+
+(TO BE WRITTEN)
+
+
+       ADDING POST-SYSTEM BUILD CONFIGURATION FILES AND EXTRA PACKAGES
+
+  The installation of BLFS packages is handled via blfs-tool and activated
+when you select the appropiate menu option. See README and README.BLFS for
+more info.
+
+  The feature descrbed below was added so users could install remaining
+configuration files, build the packages necessary to access the internet
+or to support specific hardware, or to install basic utilities that need
+have availables from the beginning, and was not intended to replace the BLFS
+install system.
+
 
   LAYOUT
   A new directory has been added to JHALFS tree which will contain the
@@ -63,10 +96,6 @@ configuration file which enables/disables the inclusion of personal scripts.
     the cmd
         make mk_CUSTOM_TOOLS
 
-  :::FINAL COMMENT:::
-    This feature was added so users could build the packages necessary to access
-    the internet and was not intended to replace the BLFS install system.
-
 
 #--------- GLIB example -----------
 

TODO

@@ -17,7 +17,8 @@ xLFS MODULES
   - To develop a new "restart" Makefile target code.
 
   - To add support for copying to the final system pre-generated
-    configuration files created by the user, if that can be implemented.
+    configuration files created by the user.
+    Work in progress via CUSTOM_TOOLS
 
 
 BLFS MODULE (See BLFS/TODO)
@@ -34,3 +35,5 @@ OTHERS
       That requires a way to can regenerate the Makefile if additional
       scripts are manually added to the *-commands/*/ dirs.
 
+    Work in progress via RE_MAKE
+

jhalfs

@@ -108,6 +108,7 @@ REPORT=${REPORT:=n}
 VIMLANG=${VIMLANG:-n}
 GRSECURITY_HOST=${GRSECURITY_HOST:-n}
 CUSTOM_TOOLS=${CUSTOM_TOOLS:-n}
+RE_MAKE=${RE_MAKE:-n}
 
 # Book surces envars
 BRANCH_ID=${BRANCH_ID:=development}
@@ -316,6 +317,8 @@ if [[ "$OPTIMIZE" != "0" ]]; then
 fi
 #
 
+if [[ "$RE_MAKE" = "n" ]] ; then
+
   # If $BUILDDIR has subdirectories like tools/ or bin/, stop the run
   # and notify the user about that.
   if [ -d $BUILDDIR/tools -o -d $BUILDDIR/bin ] && [ -z $CLEAN ] ; then
@@ -420,6 +423,8 @@ if [[ "${BLFS_TOOL}" = "y" ]] ; then
     echo "${SD_BORDER}${nl_}"
   fi
 
+fi
+
 build_Makefile
 if [[ "${PROGNAME}" = "lfs" ]]; then
   if [[ "${CUSTOM_TOOLS}" = "y" ]]; then