On Wed, 8 Mar 2017 14:41:20 -0600 [email protected] wrote: > What am I missing?
I think rhubarbpieguy is hitting at a more general issue - that the BLFS book, if followed exactly, does result in the proper *installation* of a given package, but strictly following it is not in itself sufficient to make every package *available* for further use by the system - most every package, but some, such as qt here, are exceptions. This issue is probably of most importance when porting the book's instructions into scripts - e.g., without the required updates to PATH, ldconfig, etc., later steps will fail. Of course, one could always resource, ldconfig, restart the shell, etc., after *every* package, but that would slow the build process a bit. i.e., the need to reboot or run ldconfig is generally already noted, but the need to resource, etc. isn't. (The latter is omitted only because that is supposed to be obvious to a user.) So, I think he wants a type of note at the end (e.g., a "Due to changes in the environment, the build shell will now have to be restarted for this package to be made available" boilerplate sentence) so that steps/packages that require a resource, etc., can be quickly and "fool proofly" identified as such. For without that, a person has to review the entire installation context to make a judgement (even if an easy and obvious one) about what else has to be done before proceeding to actually use the package. Just my $0.02, Mike Shell -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
