ngz pushed a commit to branch tex-team in repository guix. commit f77603ed5e7e645db789e487b05b6c8c5b8635e0 Author: Nicolas Goaziou <m...@nicolasgoaziou.fr> AuthorDate: Wed May 8 18:38:42 2024 +0200
gnu: Updated commentary in "tex.scm". * gnu/packages/tex.scm: Remove part about monolithic TEXLIVE package. Mention TEXLIVE-SOURCE and goals for TEXLIVE-BIN. Change-Id: I16adc06c808bef666cdd2393c046c6564481a22c --- gnu/packages/tex.scm | 29 +++++++++++++---------------- 1 file changed, 13 insertions(+), 16 deletions(-) diff --git a/gnu/packages/tex.scm b/gnu/packages/tex.scm index 1669135b1e..361d2f3468 100644 --- a/gnu/packages/tex.scm +++ b/gnu/packages/tex.scm @@ -117,23 +117,20 @@ ;;; The following paragraphs describe them. ;;; ;;; Guix provides two different TeX Live systems: one monolithic, the TEXLIVE -;;; package, and the other modular. Both are built from TEXLIVE-LIBKPATHSEA, -;;; which is therefore the starting of any TeX Live update. Both also rely on -;;; TEXLIVE-SCRIPTS, which contains core scripts and related files---although -;;; monolithic TeX Live only makes use of its source. At that point, both -;;; systems diverge. +;;; package, and the other modular. This module is about the latter. + +;;; Modular TeX Live source is located in TEXLIVE-SOURCE, which is therefore +;;; the starting of any TeX Live update. This is first used to build +;;; TEXLIVE-LIBKPATHSEA. It also relies on TEXLIVE-SCRIPTS, which contains +;;; core scripts and related files. Both packages are used to compile +;;; TEXLIVE-BIN, which is provided as a mandatory native input in the +;;; `texlive' build system. It includes most of the binaries, even though +;;; we're slowing building them independently. ;;; -;;; On the one hand, the monolithic TeX Live merges TEXLIVE-BIN-FULL and -;;; TEXLIVE-TEXMF in order to create TEXLIVE. -;;; -;;; On the other hand, modular TeX Live relies on TEXLIVE-BIN, which is -;;; provided as a mandatory native input in the texlive build system. Unlike -;;; TEXLIVE-BIN-FULL, it doesn't provide any script (but still include all the -;;; binaries; this might change in the future). Then the system builds its -;;; way towards regular `texlive-latex-bin' package, which is a convenient -;;; native input (that can be ignored) for most TeX Live packages. Those -;;; earlier in the build chain need the TEXLIVE-DOCSTRIP package to still be -;;; able to generate their runfiles. +;;; Then the system builds its way towards regular TEXLIVE-LATEX-BIN package, +;;; which is a convenient native input (that can be ignored or replaced) for +;;; most TeX Live packages. Packages earlier in the build chain also need the +;;; TEXLIVE-DOCSTRIP package to be able to generate their runfiles. ;;; ;;; Default font map files are updated in a profile hook (see ;;; `texlive-font-maps' in "profiles.scm"). However, this option is not