Alan Feuerbacher wrote:
On 6/9/2017 11:11 AM, Paul Rogers wrote:
The book tells me HOW to install it, I'm trying to figure out if it
needs to be installed or in what order it should be installed, e.g.
immediately after gobject? It seems like maybe it's a run-time
dependency, so maybe it can be installed at any point in the order. A
dozen or so packages refer to it as optional or recommended, but I can't
understand what makes it necessary. In the past, with this same
confusion and not building it, it SEEMS everything's been OK. But maybe
I just don't know what has been missing. Even reading its project page
at wiki.gnome.org, that seems to be address developers. Beyond
developing ways I can build and maintain my (B)LFS systems for use,
well, I *use* them. That's what I do, have always done, USE computers.
I wish there were something in the book which clarifies this confusion.
But for the moment, can someone please clarify this?
I've had similar confusions. There are many optional dependencies, some on
programs in BLFS, some on outside programs.
One thing that's often unclear is whether the optional program should be
installed *before* the program you're installing (so that the program sees
the include and library files), or whether it's strictly a run time
dependency.
The dependency needs to be installed before the package is built unless
the dependency is explicitly stated "runtime".
See
http://www.linuxfromscratch.org/blfs/view/stable/introduction/notes-on-building.html
In section "Dependencies".
I often can clear this up by doing "configure --help > configure.help" and
looking at all the flags, like --with-ldap. But sometimes even that
doesn't tell me what I want to know.
Optional software outside of BLFS is sometimes poorly documented, so
there's a lot of legwork getting it to compile and install its components
consistently with LFS. Occasionally I just give up.
Sometimes a bit more explanation about a program would be useful.
For example, systemd has its own network DNS service, but systemv does
not.
Do you mean dhcp? The DNS client is in glibc and neither system has DNS
server by default. However, configuration of DNS is slightly different in
the two versions of the book.
So in the past, I've installed dhcpcd in systemv. So now I'm
wondering whether dhcpcd would be useful for me in systemd. So far, I have
not installed it, and systemd finds my NIC without trouble. Yet another
thing I have to figure out.
A lot of things are left as a leaning exercise on purpose. For instance
the advice on configuration of different packages is purposely minimal.
In some cases whole books are written to explain the use of some packages.
As far as networking goes, the LFS systemd version of the book clearly
says (7.2. General Network Configuration):
"Starting with version 209, systemd ships a network configuration daemon
called systemd-networkd which can be used for basic network configuration.
Additionally, since version 213, DNS name resolution can be handled by
systemd-resolved in place of a static /etc/resolv.conf file. Both services
are enabled by default."
There is a LOT of information in the books now. Human nature has shown
that much of this info is either missed or forgotten.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
