On Tue, 8 Oct 2019 at 10:18, Ken Moffat via lfs-dev <[email protected]> wrote: > > On Tue, Oct 08, 2019 at 09:32:17AM +0800, Kevin Buckley via lfs-dev wrote: > > > > 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 > > > Kevin, > > maybe I'm yet again misunderstanding, but in BLFS if something is a > dependency (whether required or optional) and it has already been > installed in LFS then we don't mention it. i.e. no packages in LFS > are optional, all of them are assumed to have already been > installed.
I think the misunderstanding may be mine, especially given Bruce's: >> We are discussing adding information to LFS. I'm assuming that there's a need for a "how to re-install LFS packages" section in the BLFS Book, so that the new installs can be built against packages that they were not built against in the LFS system. However, if you look at the Dependecies Appendix in the LFS Book, you will see a number of packages, some LFS, some BLFS, and some "external" listed as "Optional dependencies". What I understand the existence of LFS packages as "Optional dependencies" for another, in the LFS Book to mean, is that a package gets installed in LFS WITHOUT regard to its "Optional dependencies". Clearly then, to my mind, on a post-LFS system, one would need to re-install the LFS package so that it now was "aware" of those Optional dependencies". Perhaps though, if your understanding is correct, then the "Optional dependencies" list in the LFS Book should not contain any LFS packages ? -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
