On Sat, 27 Feb 2021 at 11:27, Bruce Dubbs via lfs-dev <lfs-dev@lists.linuxfromscratch.org> wrote: > > We are about ready to release LFS/BLFS 10.1. All tickets have been > closed and all packages have been tested using the current instructions > in the books. > > That said, there are probably issues that still need to be addressed. > If LFS is printed out on paper, it is about 300 pages. If BLFS is > printed out paper, it is over 2000 pages. This is the last call for > change proposals before the books are released on Monday, March 1st. > > All proposals will be considered, but major changes probably will need > to be delayed until the next cycle. However, minor changes can be done > now. > > -- Bruce
Only just came to download the sources I don'r already have, for 10.1 Checking that I had them all suggests that Readline was updated, from 8.0 to 8.1, but isn't listed in the "What's new" section. I note, in the SVN log, r12069 | bdubbs | 2020-12-15 05:45:13 +0800 (Tue, 15 Dec 2020) | 9 lines Update to libcap-2.46. Update to bc-3.2.4. Update to autoconf-2.70. Update to openssl-1.1.1i. Update to Python3-3.9.1. Update to linux-5.9.14. Update to bash-5.1 and readline-8.1. so and was wondering how it gets left out ? 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? Then agsan, if the download URIs change, I coud see that you could get some false positives. And then again, there's the wget list that's not explictly in the Book but is linked to from it, so maybe that could be used as the basis for determining the diffs between versions? Just some thoughts though, Kevin -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
