On 10/8/19 2:25 AM, Kevin Buckley via lfs-dev wrote:
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.
So far there is not a 'need'. We've really not had any questions about
how to reinstall LFS packages. An information page may be desirable and
that can go at the end of LFS or the beginning of BLFS. My opinion is
that the end of LFS is slightly better.
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".
The only place there are optional packages listed from LFS is shadow
where we list acl and attr. We can move those up to the depends
section, but they really are optional. It's just that we do install
those optional packages in Chapter 6 before shadow,
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".
Not precisely. See above.
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".
Yes, but only if additional capabilities supplied by those optional
dependencies are desired. Where we've found those extra capabilities
desirable, we've added a page in BLFS with extra instructions. See, for
instance, the Python3 page in BLFS.
Perhaps though, if your understanding is correct, then the "Optional
dependencies" list in the LFS Book should not contain any LFS
packages ?
Is what we have really that confusing?
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
