This only applies to texlive source, at least for TL2023 the
x86_64 binaries include luametatex. For source the luametatex
sources are not included. In the unlikely case that we have a
user who both builds texlive from source and uses context, let
them know before we release 12.0 in case another luatex
vulnerability is discovered before TL2024.
In 2023 we eventually discovered that the x86_64 binaries for
asymptote had not worked for at least 2 years, and we now have
a workaround for that. My 20230807 files are intended to show
which *collections* need to be added to schme-medium to allow
the various tests to run.
Also create an ENTITY for qt5 or qt5-alternate and use that
to specify the qt5 dependenies.
The complete KF5/plasma packages should use the full qt5 build, but
the lxqt kf5/plasma components only need qt5-alternate.
Well, my script did not handle package names with dashes correctly. So
some User Note links were mistakely removed. Recheck removed links
containing dashes and add them back if applicable.
So we can simply the instruction. Also remove a stale command
explanation referring to "configure script" (we are using meson now).
Simply the explanation for libkpathsea.so symlink in texlive too as we
don't distinguish "old" and "new" evince installations anymore. The
original explanation emphasizing "old" evince installation also does not
make sense to me: we have /etc/ld.so.conf addition which should be
enough for ld.so to find libkpathsea.so.6 when evince is used; and ld.so
only searches for "libkpathsea.so.6" (which is a DT_NEEDED entry in
evince libdvidocument.so), not unversioned libkpathsea.so.
We usually put those additions in the page where we define all the
paths. So move this one to "Setting the PATH for TeX Live". This
also prevents having to edit the texlive script in jhalfs (to
remove the addition when reinstalling).
Grammar.
In explanations, options come after commands. Add comment on
other accepted options which are used by some distros but have
no real benefit in this source build.
Use scripts so that 'mkiv' (based on luatex) will work,
rather than requiring extra package 'luametatex' which
is very different from the rest of texlive.
Move it from before configuring dvisvgm to after installing
texlive. For dvisvgm there is no difference, but this ensures that
an existing version of evince linked against kpathsea can work
after texlive/2022 is replaced by texlive/2023.
Now all sourceforge.net subdomains have a valid SSL certificate. The
changes are automatically done via a sed. I've reviewed the changes and
reverted the changes in archive/*, pst/xml/docbook-xsl.xml, and
stylesheets/lfs-xsl/lfs-l10n.xml. Other changes should (hopefully) be
fine.
Also corrected the capitalization of titles and cleaned up some
grammatical errors. Note that a few modules quote the "config"
menu for the Linux kernel, whch says "user-space". Those
modules were not altered; directly quoted material should be
reproduced verbatim.
In this version of ghostscript, some private symbols have been
hidden. One of the private symbols is gs_error_names, which is used
by dvisvgm. Fortunately, dvisvgm, has already the infrastructure
for this case, since private symbols are always hidden in Windows.
Upstream has a patch:
https://github.com/mgieseki/dvisvgm/commit/9bf81fd0
which can be reduced to a sed.
Remove --enable-dynamic: upstream have hidden symbols in their shared
libraries because they were getting conflicts with other symbols in
some cases. The problem then is that the shared object X11.so module
symbols cannot be found by X11 libraries when loaded dynamically.
The solution is to have the module statically linked into the gs
binary itself (findings by Xi Ruoyao. removing --enable-dynamic is
upstream's advice).
Moved the profile script to texlive.sh from extrapaths.sh.
Created an environment variable TEXLIVE_PREFIX and incorporated
it into the chapter's build scripts.
An additional optimization can still be made by moving the
TEXARCH variable into texlive.sh and removing it from
package instructions.
