Miscellaneous tweaks found while removing clfs

README.CUSTOM

@@ -110,7 +110,8 @@ configuration file which enables/disables the inclusion of custom scripts.
           are built in the right order.
 
   1. To add a package to the final JHALFS Makefile you must first create a file
-     in the custom/config directory.
+     in the custom/config directory. The directory custom/config may need
+     to be created first.
        **All config files MUST follow the naming convention, xxx-PKG, where xxx
        is the order number and PKG is the name of the package. The file naming
        format is important as it defines the build order. The example shown

README.PACKAGE_MANAGEMENT

@@ -18,12 +18,11 @@ BY    : Pierre Labastie (work in progress)
 
       For now, package management is only available for LFS. The `porg style'
   (see below) package management has been ported to BLFS, but not the distro
-  style one (the book layout makes it rather difficult). I have not attempted
-  to adapt this tool for the other flavours of LFS (TODO).
+  style one (the book layout makes it rather difficult).
 
       This tool comes in two flavours:
   - for distros package managers (e.g dpkg or pacman), it basically performs
-    a "DESTDIR install" for all pages in chapter 6, 7 and 8 of the book. The
+    a "DESTDIR install" for all pages in chapter 8, 9 and 10 of the book. The
     name of the DESTDIR directory is the same as the one of the executed
     script. The path to this directory is available to the scriplets through
     the PKG_DEST variable. The details of the DESTDIR part are given below.
@@ -44,7 +43,7 @@ BY    : Pierre Labastie (work in progress)
       Note that with carefully crafted "packInstall" and "wrapInstall"
   functions, a combination of the two methods could be used, for example for
   DESTDIR installs using fakeroot. This is work in progress and not fully
-  implemented yet.
+  implemented yet (well... Closer to a wish list actually).
 
 3. DETAILS:
 
@@ -61,7 +60,7 @@ BY    : Pierre Labastie (work in progress)
   binary package.
 
       In order to use the package manager, it has to be installed at the end of
-  chapter 5 (temporary installation in /tools) and chapter 6 (final install).
+  chapter 7 (temporary installation) and chapter 8 (final install).
   Furthermore, the administrative files and directories have to be created
   during the `Creating Directories' and `Creating Essential Files' stages.
   For all this, the user has to supply a file in docbook XML format, with

TODO

@@ -1,6 +1,7 @@
             jhalfs TODO
           ---------------
-
+look at func_download_packages: use cat urls.lst |while read ...
+instead of for line in $(cat urls.lst)
 
 BLFS MODULE (See BLFS/TODO)
 -----------