Changeset 2ee1d11 for README.BLFS
- Timestamp:
- 10/07/2006 07:14:47 PM (18 years ago)
- Branches:
- experimental
- Children:
- 42e1b38
- Parents:
- f5791f0
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
README.BLFS
rf5791f0 r2ee1d11 9 9 dependencies will be used, etc. 10 10 11 Said that, the goal of jhalfsis try to help you solving packages12 dependencies and creating your own build scripts /Makefile. Someof the13 auto-generated build scripts and Makefile could work "as is", butas a11 Said that, the goal of blfs-tool is try to help you solving packages 12 dependencies and creating your own build scripts and Makefile. Few of the 13 auto-generated build scripts and Makefile could work "as is", thus as a 14 14 general rule you will need to review and edit the scripts while reading 15 15 the book. 16 17 NOTE:: The code is still under development and may contains several bugs18 16 19 17 … … 28 26 (user error, package bug, BLFS command bug, or jhalfs code bug) 29 27 30 If you do n't have the above skill, please don't use this tool.28 If you do not have the above skills, please don't use this tool. 31 29 32 30 33 31 3. USAGE:: 34 32 35 Due the complexity of the BLFS book, the scripts /Makefile generation is33 Due the complexity of the BLFS book, the scripts and Makefile generation is 36 34 done in several steps: 37 35 38 3.1 INSTALLATION:: 36 3.1 INSTALLED PACKAGES TRACKING SYSTEM 37 38 This tool includes a very simple tracking system to know what packages 39 has been installed using the tool. It is used to skip installed packages 40 from target selection menu and to know if an installed package has been updated 41 on the BLFS book. Don't rely on this feature as a packages management tool. 42 43 The directory where tracking files will be stored need be created 44 before installing blfs-tool. You can place that directory anywhere, taking 45 care that the builder user must have read and write privileges on that 46 directory and on all files it contains. 47 48 To use the default path set in the installation menu, run as root: 49 50 install -d -m1777 /var/lib/jhalfs/BLFS 51 52 3.2 BLFS_TOOL INSTALLATION:: 39 53 40 54 Run "make" to launch the jhalfs menuconfig interface. Select the BLFS 41 55 book and it version. Then set the installation directory (default 42 $HOME/blfs_root) and the BLFS sources directory (default blfs-xml). 56 $HOME/blfs_root), the BLFS sources directory (default blfs-xml), and 57 the installed packages tracking directory (default /var/lib/jhalfs/BLFS). 43 58 44 59 All required files will be placed in the installation directory and … … 70 85 root directory. 71 86 72 3.2 UPDATING BOOK SOURCES:: 87 When finished the installation, the configuration and target selection 88 menu is launch. 89 90 3.3 UPDATING BOOK SOURCES:: 73 91 74 92 If using the development book version, and if you want to update already … … 76 94 the XML sources and packages database. 77 95 78 To do that run "./update_book.sh" 79 80 3.3 CONFIGURING AND PARSING THE BOOK:: (obsolete, to be rewritten) 96 To do that run "./update_book.sh" 97 98 On the next configuration run, packages already installed but listed 99 with a new version in the book will be available for target selection and 100 used to solve dependencies. 101 102 3.4 CONFIGURING AND PARSING THE BOOK:: 81 103 82 104 Next step is to create a book and build scripts in dependencies build order 83 for a target package. A target package can be any of the ones listed in the 84 packages file. That is done using the blfs-parser.sh script, but we are trying 85 to make a menuconfig based system. 86 87 The script need three arguments: 88 89 package name as listed in packages file 90 dependencies level 1 for required, 91 2 for required an recommended 92 3 for required, recommended, and optional 93 sudo usage y if sudo will be used (you want build as a normal user) 94 n if sudo isn't needed (you want build as root) 95 96 For example: 97 98 ./blfs-parser galeon 3 y 99 100 will create a directory named "galeon". Inside that directory you find a 101 directory named "HTML" that contains a galeon-based HTML book with all 102 dependencies in build order and a "scripts" directory with build scripts 103 that uses sudo for commands that need root privileges. 104 105 There is also two other directories, dependencies and xincludes, that 105 for a target package. A target can be a package or a meta-package. 106 107 Run <make> to launch the configuration interface. The main menu contains 108 three block: meta-package selection, individual package selection, and 109 build options. 110 111 Only one meta-package or individual package must be selected on each run. 112 That is due that there is no way to solve dependencies properly when 113 more than one target are selected at the same time. 114 115 When a meta-package is selected is possible to unselect unwanted components. 116 That unselected components will be skipped if no other components depends 117 on them. 118 119 In the build options section the dependencies level and default packages 120 used to solve alternatives are set. Can be set also if the build will be 121 made as a normal user or as root. That settings are saved to be reused on 122 future configuration runs. 123 124 If, for example, your target selection is Xsoft-->Graphweb-->galeon a 125 directory named "galeon" will be created. Inside that directory you will 126 find a directory named "HTML" that contains a galeon-based HTML book with 127 its dependencies in build order, and a "scripts" directory with build 128 scripts for that packages. 129 130 There is also two other directories, "dependencies" and "xincludes", that 106 131 contains files generated while resolving dependencies trees. 107 132 108 3. 4EDITING BUILD SCRIPTS109 110 Now is t he time to review the generated book and scripts, making in the133 3.5 EDITING BUILD SCRIPTS 134 135 Now is time to review the generated book and scripts, making in the 111 136 scripts any changes required to fix generation bugs or to fit your needs. 112 137 … … 117 142 script. 118 143 119 Notethat the packages tracking system isn't a packages management tool144 Remember that the packages tracking system isn't a packages management tool 120 145 and know nothing about packages not in the BLFS book. 121 146 122 3.5 CREATING THE MAKEFILE 147 Also, review and edit envars.conf. That file is used to set global envars 148 needed by the build scripts. 149 150 3.6 CREATING THE MAKEFILE 151 123 152 When the build scripts are ready to be run, the Makefile can be 124 153 created. Be sure that you cd into the "package" directory and run … … 126 155 ../gen_makefile.sh 127 156 128 Review the Makefile and if all look sane, start the build. 129 130 131 (Text is needed about meta-packages, the installed packages tracking system 132 and like) 133 134 (The TRACKING_DIR directory must be created before using this tool running as root 135 136 install -d -m1777 /var/lib/jhalfs/BLFS ) 157 Review the Makefile and if all looks sane, start the build. 137 158 138 159 4. GENERATED BUILD SCRIPTS ISSUES:: … … 177 198 178 199 Also, you will need to edit the scripts to fix the commands that must 179 be applied only to a concret individual sub-package. For example the "for"180 loop to install xo tg7-util packages may read like:200 be applied only to a concrete individual sub-package. For example the "for" 201 loop to install xorg7-util packages may read like: 181 202 182 203 for package in $(cat $WGET_LST) ; do
Note:
See TracChangeset
for help on using the changeset viewer.