Add an explanation to the Conventions page about SBU times when using parallel

build procedures.

Set defailt MANPATH and INFOPATH values in /etc/profile.d/extrapaths.sh.


git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@14641 af4574ff-66df-0310-9fd7-8a98e5e911e0
This commit is contained in:
Bruce Dubbs 2014-10-17 02:17:11 +00:00
parent 16890f2a18
commit bfa21f3653
3 changed files with 28 additions and 0 deletions

View File

@ -47,6 +47,14 @@
<listitem>
<para>October 16th, 2014</para>
<itemizedlist>
<listitem>
<para>[bdubbs] - Add an explanation to the Conventions page
about SBU times when using parallel build procedures.</para>
</listitem>
<listitem>
<para>[bdubbs] - Set defailt MANPATH and INFOPATH values
in /etc/profile.d/extrapaths.sh.</para>
</listitem>
<listitem>
<para>[fernando] - Update to seamonkey-2.30. Fixes
<ulink url="&blfs-ticket-root;5688">#5688</ulink>.</para>

View File

@ -123,4 +123,20 @@ EOF</userinput></screen>
</sect2>
<sect2>
<title>SBU values in BLFS</title>
<para>As in LFS, each package in BLFS has a build time listed in Standard
Build Units (SBUs). These times are relative to the time it took to build
binutils in LFS and are intended to provide some insight into how long it
will take to build a package. Most times listed are for a single processor
or core to build the package. In some cases, large, long running builds
tested on multi-core systems have SBU times listed with comments such
as '(parallelism=4)'. These values indicate testing was done using
multiple cores. Note that while this speeds up the build on systems with
the appropriate hardware, the speedup is not linear and to some extent
depends on the individual package and specific hardware used. </para>
</sect2>
</sect1>

View File

@ -230,6 +230,10 @@ fi
if [ -d /usr/local/sbin -a $EUID -eq 0 ]; then
pathprepend /usr/local/sbin
fi</literal>
# Set some defaults before other applications add to these paths.
pathappend /usr/share/man MANPATH
pathappend /usr/share/info INFOPATH
EOF</userinput></screen>
</sect3>