Changeset 2257bd7


Ignore:
Timestamp:
10/14/2021 06:51:49 AM (3 years ago)
Author:
Pierre Labastie <pierre.labastie@…>
Branches:
ablfs-more, legacy, trunk
Children:
2718053
Parents:
e22aa96
Message:

Update and fix documentation of custom tools

Files:
4 edited

Legend:

Unmodified
Added
Removed
  • README.CUSTOM

    re22aa96 r2257bd7  
    6060  To replace a package by an equivalent one, rename the replaced package script
    6161to reflect the new package name (for example, 102-man-db -> 102-man), edit the
    62 script to made the required commands changes, place the new tarball in the
     62script to make the required commands changes, place the new tarball in the
    6363${BUILD_DIR}/sources directory, and edit ${BUILD_DIR}/${SCRIPT_ROOT}/pkg_tarball_list
    6464file to replace the removed package tarball name by the new package tarball
     
    9999install system.
    100100
    101   :::NOTICE:::
    102   The following examples are for use with LFS and are not applicable to any
    103 of the CLFS-sysroot or CLFS-Embedded books. The directory examples_CLFS-E
    104 contains code extracted from Beyond CLFS-embedded. Any packages you chose to
    105 add should honour the DESTDIR=${CLFS} switch or equivalent.
    106 
    107 
    108101  LAYOUT
    109102  A new directory has been added to JHALFS tree which contains the
     
    133126
    134127  2. Populate the variables with the necessary values.
    135        Variable function is self explanatory except for the inclusion of the
    136        build cmds. If the package you want to include is found in the BLFS
    137        book then you only need to copy/paste the cmd strings between the xEOFx
    138        pairs, otherwise you will need to define the build cmds yourself.
     128       Variable function is self explanatory. PATCH variables must be
     129       numbered, starting at PATCH1 (up to PATCH10). If the md5 checksum value
     130       is known, it can be added after the URL as in (quotes needed):
     131       PATCH1="http://patch-host/patch-path xxxxxxx..."
     132
     133  3. Build commands
     134       If the package you want to include is found in the BLFS
     135       book then you only need to copy/paste the commands between the xEOFx
     136       text, otherwise you will need to define the commands yourself.
    139137     NOTE::: This script you just created is not usable directly but contains
    140138             all the information necessary for jhalfs to create a build script
    141139             and an entry in the jhalfs Makefile.
    142140
    143   3. As mentioned previously the build order is dictated by the 3 digit number
     141  4. As mentioned previously the build order is dictated by the 3 digit number
    144142     in the file name. If a package has dependencies it must be numerically
    145143     larger than the dependency files.
    146        i.e. The package mc has glib as a dependency and build order is
     144       e.g. The package mc has glib as a dependency, so the build order is:
    147145           950-glib
    148            951-mc
    149 
    150   4. A config file for BLFS-bootscripts is already created as 999-blfs_bootscripts.
     146           951-mc
     147
     148  5. A config file for BLFS-bootscripts is already created as 999-blfs_bootscripts.
    151149     If a package requires a bootscript to be installed add the cmd to this
    152150     file and NOT in the package script. The gpm script is included as an
    153      example of multiple patch files and the need for a blfs bootscript.
     151     example of patch file and the need for a blfs bootscript.
     152
     153
     154  EXAMPLES
     155
     156    Other examples can be found in custom/examples. They are dated and
     157    unmaintained, but can be useful for creating your own scripts.
     158
     159  :::NOTICE:::
     160  The following examples are for use with LFS and are not applicable to any
     161of the CLFS-sysroot or CLFS-Embedded books. The directory examples_CLFS-E
     162contains code extracted from Beyond CLFS-embedded. Any packages you chose to
     163add should honour the DESTDIR=${CLFS} switch or equivalent.
    154164
    155165
     
    174184  # Patches are named PATCH[1..10]
    175185  # This information is used to download the patch only
    176   # If you do not have the MD5SUM the download will proceed with a warning.
    177186PATCH1="http://www.linuxfromscratch.org/patches/blfs/svn/glib-1.2.10-gcc34-1.patch 0077a1cce5e8a2231ac5a9b08c6263ba"
    178187
     
    205214   unset $i
    206215done
    207   # MD5SUM is not absolutely necessary but JHALFS whines and complains
    208   # Add the MD5SUM if you can
    209216PATCH1=" http://www.linuxfromscratch.org/patches/blfs/svn/gpm-1.20.1-segfault-1.patch"
    210217PATCH2=" http://www.linuxfromscratch.org/patches/blfs/svn/gpm-1.20.1-silent-1.patch"
     
    264271xEOFx
    265272) > tmp
    266 
  • custom/examples/941-pcre

    re22aa96 r2257bd7  
    1010   unset $i
    1111done
    12 PATCH1="http://www.linuxfromscratch.org/patches/blfs/7.8/pcre-8.37-upstream_fixes-1.patch 718c4314fba52ed559c75ff7660cc391"
     12PATCH1="https://www.linuxfromscratch.org/patches/downloads/pcre/pcre-8.37-upstream_fixes-1.patch 718c4314fba52ed559c75ff7660cc391"
    1313
    1414( cat << "xEOFx"
  • custom/examples/963-gpm

    re22aa96 r2257bd7  
    55PKG_VERSION="1.20.7"
    66PKG_FILE="gpm-${PKG_VERSION}.tar.bz2"
    7 URL="http://www.nico.schottelius.org/software/gpm/archives/${PKG_FILE}"
     7URL="https://anduin.linuxfromscratch.org/BLFS/gpm/${PKG_FILE}"
    88MD5="bf84143905a6a903dbd4d4b911a2a2b8"
    99for i in PATCH{1..10}; do
    1010   unset $i
    1111done
     12PATCH1="https://www.linuxfromscratch.org/patches/blfs/svn/gpm-1.20.7-consolidated-1.patch"
    1213
    1314( cat << "xEOFx"
    1415
    15 ./autogen.sh                                &&
    16 ./configure --prefix=/usr --sysconfdir=/etc &&
     16patch -Np1 -i ../gpm-1.20.7-consolidated-1.patch &&
     17./autogen.sh                                     &&
     18./configure --prefix=/usr --sysconfdir=/etc      &&
    1719make
    1820
     
    2224             /usr/share/info/gpm.info                 &&
    2325
     26rm -fv /usr/lib/libgpm.a                              &&
    2427ln -sfv libgpm.so.2.1.0 /usr/lib/libgpm.so            &&
    2528install -v -m644 conf/gpm-root.conf /etc              &&
    2629
    27 install -v -m755 -d /usr/share/doc/gpm-${PKG_FILE}/support &&
     30install -v -m755 -d /usr/share/doc/gpm-1.20.7/support &&
    2831install -v -m644    doc/support/*                     \
    29                     /usr/share/doc/gpm-${PKG_FILE}/support &&
     32                    /usr/share/doc/gpm-1.20.7/support &&
    3033install -v -m644    doc/{FAQ,HACK_GPM,README*}        \
    31                     /usr/share/doc/gpm-${PKG_FILE}
     34                    /usr/share/doc/gpm-1.20.7
    3235
    3336# The normal cmd to install the boot script for gpm
  • custom/template

    re22aa96 r2257bd7  
    1414done
    1515PATCH1=""
     16# Up to 10 patches can be added. The PATCH variable must be numbered
     17# even if there is only one. If the patch md5 checksum is known, add
     18# it after the name as in (quotes are required):
     19# PATCHx="patch-url md5"
    1620
    1721( cat << "xEOFx"
    18 
     22# Your script here. Be aware that it is passed
     23# verbatim, and that none of the above variables
     24# will be defined when running the script. For example,
     25# If you want to use ${PKG_VERSION}, you have to
     26# redefine it here.
    1927xEOFx
    2028) > tmp
Note: See TracChangeset for help on using the changeset viewer.