On Wed, Jan 10, 2018 at 6:07 PM, Pierre Labastie <[email protected]> wrote:
> > I do not do systemd. I guess I'll have to some day, but there is a learning > stage I'm reluctant to spend time with. > > :) I work in academia. Academics are among the most stubborn when it comes to accepting changes to their habits. If the boot process can happen in parallel, I'm all for it. > > > > > > > --- > > > cURL-7.57.0 -> Installation of cURL -> Dependencies > > > libmetalink is listed as optional in the dependencies, but an > explicit > > > --with-libmetalink to configure is required to include it. > > > --- > > > > Actually, we try to put in the optional dependencies of a package, > anything > > that can be used by that package. As written on the "Notes on > Building > > Software" page, we often describe what functionality is added by the > > dependency. But we almost never give the instructions to include the > optional > > dependencies. > > > > > > Ok. It's just that the way the instructions are written, i.e. suitable > for copy > > & paste into a terminal, most readers will not see the configure > summary. They > > will continue thinking the optional dependency was used. I check the > configure > > log, so really I'm just pointing this out in case it's worth considering. > > > > Maybe we should be more explicit that when including optional deps, users > are > on their own. We only test recommended deps (on a regular basis). Not > enough > man power to test everything. > > Along the lines of Bruce's suggestion for a comment in the dependencies section, how about something like: Notes on Building Software -> Dependencies Optional means that ... Note that the functionality provided by the dependency may require an explicit option/switch (?) to configure in order to be enabled.
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
