Changeset 347e59c for pst/typesetting/typesetting.xml

Timestamp:

01/11/2015 09:06:00 PM (9 years ago)

Author:

Ken Moffat <ken@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

b2d5567

Parents:

0d36568

Message:

Add separate asymptote and indy. Various consistency edits and rephrasing Texlive pass 1 now describes itself as just texlive from source, the original texlive page is no longer rendered : I will archive the latter and then rename the pass1 file in later commits, then look at what might optionally xref to the binary page.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@15327 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• pst/typesetting/typesetting.xml (modified) (1 diff)

pst/typesetting/typesetting.xml

@@ -29 +29 @@
   <command>tlmgr</command> to update their system.</para>
 
-  <para>Most people reading BLFS will wish to build from source. You can either
-  do as BLFS used to do, by starting with <application>install-tl-unx</application>,
-  or you can avoid the binary files completely and begin at
-  <xref linkend="texpass1"/> which will install most of
+  <para>Most people reading BLFS will wish to build from source. BLFS used to
+  start by installing <application>install-tl-unx</application> and then use that
+  to bootstrap the build.  Nowadays, we build almost the whole of
+  <application>texlive</application> <emphasis>without</emphasis> a binary install,
+  by adding the separately-packaged texmf files into this build.  For this, begin
+  at <xref linkend="texlive"/> which will install most of
   <application>texlive</application>, together with <emphasis>all</emphasis> of the
-  supporting files. This almost-complete install is then used to build two
-  remaining parts of <application>texlive</application>, xindy and asy (that
-  involves recompiling all of the package, but not reinstalling all of it).</para>
+  supporting files. This almost-complete install can then be used to build the
+  remaining parts of <application>texlive</application>, <xref
+  linkend="asymptote"/>, <xref linkend="xindy"/> and <xref linkend="biber"/>.
+  </para>
 
   <para>Because the texmf files (including documentation, fonts, scripts and
   supporting files) are all in one tarball, it is not practical to limit what
   gets extracted in a sensible way (e.g. to exclude one or other of the typesetting
-  engines).</para>
+  engines) when building from source in this manner.</para>
 
-  <para>After that, people building from source will wish to install <xref
-  linkend="biber"/>, which is supplied separately, to complete the full
-  installation.</para>
+  <para>In either case, BLFS installs into
+  <filename class="directory">/opt/texlive/&texlive-year;</filename> with the sole
+  exception of two libraries from the source install which are installed into
+  <filename class="directory">/usr/lib</filename> for convenience.</para>
 
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="tl-installer.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="texlive-pass1.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="tex-path.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="texlive.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="biber.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="xindy.xml"/>
 
 </chapter>