Changeset f222bb8
- Timestamp:
- 11/10/2006 02:32:24 PM (17 years ago)
- Branches:
- 2.3, 2.3.x, 2.4, ablfs, ablfs-more, legacy, new_features, trunk
- Children:
- e66ee70
- Parents:
- a2133cb
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
README.CUSTOM
ra2133cb rf222bb8 15 15 boot and work with. Each one of this areas is handled in a diferent way. 16 16 17 18 19 17 20 BASE SYSTEM CUSTOMIZATION 18 21 … … 29 32 This is the method discussed below. 30 33 31 (TO BE WRITTEN) 34 35 EDITING THE BASE SCRIPTS 36 37 Fisrt step is to generate the build scripts with book defaults. To do that, 38 configure jhalfs activating any option you want included, but do not select 39 "Run the Makefile" option. 40 41 Under the ${BUILD_DIR}/${SCRIPT_ROOT}/${PROGNAME}-commands directory 42 (using the defaults values to do an LFS build, that directory name is 43 /mnt/build_dir/jhalfs/lfs-commands) you will find the default build scripts. 44 45 If all you want is modify, add, or remove some command from a package 46 installation, for example to change it ./configure line, just edit the related 47 script. If changing or adding a patch, be sure to copy the new patch to the 48 ${BUILD_DIR}/sources directory. When done, run 'make' from inside the 49 ${BUILD_DIR}/${SCRIPT_ROOT} directory. 50 51 52 REPLACING OR INSERTING PACKAGES AND CHANGING BUILD ORDER 53 54 To remove a package from the system, just remove its script(s). 55 56 To change the version of some package to build a newest or oldest one than the 57 one found in the book, edit ${BUILD_DIR}/${SCRIPT_ROOT}/pkg_tarball_list to 58 change it tarball name and place the new tarball in the ${BUILD_DIR}/sources 59 directory, 60 61 To replace a package by an equivalent one, rename the replaced package script 62 to reflect the new package name (for example, 102-man-db -> 102-man), edit the 63 script to made the required commands changes, place the new tarball in the 64 ${BUILD_DIR}/sources directory, and edit ${BUILD_DIR}/${SCRIPT_ROOT}/pkg_tarball_list 65 file to replace the removed package tarball name by the new package tarball name. 66 67 To change the build order, rename the scripts changing the first 3-digits 68 string until have it ordered in the way you want. 69 70 To insert a new package, for example to build Cracklib to can build Shadow 71 with Cracklib support, first you should decide before what default package it 72 need be installed, in this example before 107-shadow. Then create a new script 73 containg the needed commands, using an existing one as template, and name it with 74 the same 3-digits string used for that mentioned default package, but adding 75 another 1-digit string. In our example, the new script to build Cracklib just 76 before Shadow will be named 107-1-cracklib. This naming schema allow to insert 77 up to 10 scripts before each one of the default scripts. Place the tarball for 78 the new package and required patches, if any, if ${BUILD_DIR}/sources and edit 79 ${BUILD_DIR}/${SCRIPT_ROOT}/pkg_tarball_list to add the tarball name for that 80 package. 81 82 When ready, launch again the jhalfs configuration interface. Be sure that 83 are selected exactly the same options than when generating the default build 84 scripts. Be sure that "Rebuild files" is unselected and select "Run the Makefile" 85 if you want. Then select "Rebuild the Makefile". This will create a new Makefile 86 based on the changes you made to the build scripts. 87 88 32 89 33 90
Note:
See TracChangeset
for help on using the changeset viewer.