On Wed, 3 Mar 2021 at 01:04, Bruce Dubbs <bruce.du...@gmail.com> wrote: > > > > FWIW, I do something akin to > > > > links2 -width 132 -dump -html-numbered-links 0 LFS-BOOK-10.1-NOCHUNKS.html > > | \ > > grep Download: \ > > cut -d/ -f 3- > LFS-BOOK-10.1-SRC_PATHS.txt > > > > to get a list of "paths to" each Book's sources, so was wondering > > if something like that list being maintained, on the backend, might > > help in autogenerating the "What's new" list? > > I think that's a little more effort than it's worth. It's part of my > routine to update the "What's new" list when I update the change log. > Readline is a little different because it is pretty tightly coupled to bash. > > Thanks for pointing out the problem though. > > -- Bruce
What can i tell you: the problem affected "my distro: my build process", so I noticed it. Just to develop on the way I go about storing the sources though, in case it might help automate things a littlle more, Clealry, I am storing the sources below a path tree that matches the URIs. However, I also use the package URIs in my own instructions for building things. I am aware that LFS expects the user to have all the sources unpacked, somewhere, and doesn't provide explict instructions for doing so, nor for changing into the package's source directory, at the package level, but I have found that doing something akin to export SOURCE=`echo &dejagnu-url; | cut -d/ -f 3-` tar xf $LFSSRCS/$SOURCE cd dejagnu-&dejagnu-version is a bit more explict and ties in nicely to the predefined Entities that the Book sources already proivde, so as to give a deterministic set of instructions. Just food for thought though: feel free to spit it out if you don't like it! Kevin -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
