Changeset b15261a for README.BLFS
- Timestamp:
- 08/12/2017 01:03:06 PM (7 years ago)
- Branches:
- ablfs-more, legacy, trunk
- Children:
- ce244f6
- Parents:
- 6d1d77c
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
README.BLFS
r6d1d77c rb15261a 14 14 you will need to review and edit the scripts while reading the book. 15 15 16 Since version 3.0 of jhalfs, the blfs tools allow also to update packages 17 from the LFS book. LFS packages which may be updated appear in the menu 18 interface. When selected, their scriptlet is generated in the same manner 19 as for BLFS packages. 16 20 17 21 2. PREREQUISITES:: … … 65 69 their being present. 66 70 71 - In this case, the tool has no way to know which version of LFS packages 72 is installed, so that the menu interface will show all the LFS packages, 73 as if they were not installed. If you have a released version of LFS, or 74 the date of your SVN version of LFS is known, you should run the 75 update-lfs.sh script. If you have updated some 76 LFS packages since first installation, or have been using a custom 77 working copy of the LFS book, the only (tedious) way is to create 78 empty files with names <package>-<installed-version> in the tracking 79 directory, and run the tool. 80 81 - If you have also installed some BLFS packages, they are not in the 82 tracking file. The only way is to create empty files with names 83 <package>-<installed-version> in the tracking directory, and run the tool. 84 67 85 3.2 INSTALLATION ON A JUST BUILT xLFS SYSTEM 68 86 … … 94 112 above 95 113 114 - Note that the versions of LFS packages are automatically known to 115 the tool in this case, and there is no need to run the update-lfs.sh 116 script. 117 96 118 We assume that the BLFS tools will be used on a booted xLFS system. 97 119 Using them to build BLFS packages in a chroot jail is also possible, … … 101 123 102 124 blfs-xml/* SVN tree of the selected BLFS book version 125 lfs-xml/* SVN tree of the selected LFS book version 103 126 lib/constants.inc functions libraries 104 127 /func_dependencies for building the dependency tree … … 110 133 of a package 111 134 /make_book.xsl XSL stylesheet to generate the linear book.xml 135 /lfs_make_book.xsl XSL stylesheet to incoporate LFS pages into the 136 linear book.xml 112 137 /scripts.xsl XSL stylesheet to generate the scriptlets from 113 138 book.xml … … 128 153 envars.conf envars needed when running the target build scripts 129 154 130 155 Working files: several files are generated when first running the tool 131 156 132 157 packages.xml auto-generated packages database … … 236 261 just need to create a "064-y-bar" build script. 237 262 238 Remember, the package tracking system isn't a package management tool263 Remember, the package tracking system isn't a package management tool 239 264 and knows nothing about packages not in the BLFS book. 240 265 241 Also, review and edit envars.conf. This file is used to set global envars 242 needed by the build scripts. 266 IMPORTANT: Review and edit envars.conf, at least after installing the 267 tool. This file is used to set global envars needed by the build scripts. 268 If you use package management, the variable PACK_INSTALL should point to 269 where the packInstall.sh script resides. 243 270 244 271 4.4 CREATING THE MAKEFILE::
Note:
See TracChangeset
for help on using the changeset viewer.