On Mon, 7 Oct 2019 at 23:48, Bruce Dubbs via lfs-dev <[email protected]> wrote: > > > I think the above is way too much. Upon thinking about it, expanding > the page in section "9.4. What Now?" should be sufficient. > > Generally, packages can be rebuilt with LFS instructions after the > additional dependencies are installed. A list of these similar to the > changelog format or the BLFS 'Command Explanations' format would do the > job. At each entry, it would list the dependencies you mention below > and when appropriate a link to the BLFS page with supplementary > instructions. > > Also updating a package to a new version can almost always be done in > place. The only exception would be glibc. If that needs to be updated, > I feel the whole system needs to be rebuilt. > > -- Bruce
Fair enough: cancertainly give that a go. To that end though, a couple of other, related, RFCs 1) Within the LFS Book's "Optional dependencies" lists, there are a number of references to LFS packages (see the list I re-rendered), however, when we move across into the BLFS Book, those packages don'r exist, so one would need a way to refer back to the LFS Book section 2) (This one I may have raised before? I certainly remember being aware of it for some time now) At a number of places in the BLFS Book (15, according to a search, across the single page BLFS Book, for "lfs/view") there are references to sections within the LFS Book, however all 15 are rendered with respect to what I assume is the SVN layout on the main LFS repo server, so, for example, the first of the 15 is this one (line wrapped for easy identification): ----8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<---- BLFS Boot Scripts The BLFS Bootscripts package contains the init scripts that are used throughout the book. It is assumed that you will be using the BLFS Bootscripts package in conjunction with a compatible LFS-Bootscripts package. Refer to ../../../../lfs/view/9.0/chapter07/bootscripts.html for more information on the LFS-Bootscripts package. ----8<--------8<--------8<--------8<--------8<--------8<--------8<--------8<---- Note the file URI and the file path back to the target of the link. I'm thing that URI should probably point to a target in the online rendering of the LFS Book at the website, and/or have some kind of alternative file based URI with the target as a <linkend> rendered as though one were already in the LFS Book. The latter allows for someone reading the Books offline to navigate within each Book, even if their offline copies are not laid out, within their filesystem in the same way that the LFS's repo/website is. Kevin -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
