%general-entities; ]> When you're going to update the book by adding a new package to it, here's how you do it: Assign yourself to the ticket for this new package. Test build an LFS system to make sure this package compiles properly in an LFS environment. Don't use your regular workstation's environment - it may be sufficiently different for the compilation to abort. A package may depend on something that you have installed but which doesn't come with the LFS-Book. Also keep in mind that some packages are used twice, in chapter 5 and in chapter 6. Update the installation instructions in the book, if necessary. When the package compiles properly and the package works too (doesn't seg. fault or show other errors when trying to execute programs from it), then open the entities/general.ent in an editor. Find the package-version entity and update its value to the new version. Update the list of files installed by the new version of the package. This can be trivially gathered by using find immediately prior to and immediately after installing the new version and diffing the output. We now prefer to use the package's native format (so that md5sums or signatures can be checked) instead of creating a .tar.bz2 if the package is supplied only in .tar.gz. The maintenance of package versions on the LFS mirrors is handled separately, and there is no longer a need to copy new versions of packages to your home directory. Run ls -l package-version.tar.{bz2,gz} on the source tarball. Divide the filesize by 1024 to get the number of Kilobytes. Round off to the nearest Kilobyte and update the package-size entity.