The texlive binaries are built with RPATH, thus they work fine w/o
ld.so.conf modification.
For other packages using kpathsea we need to symlink libkpathsea.so.6 to
/usr/lib so it can be found.
It seems install-tl-unx does not use texlive shared libraries at all (I
downloaded the tex executable from it and the executable only uses
libc.so.6 and libm.so.6).
neither firefox nor epiphany can download them, and they are not
well maintained, because rarely tested.
This is WIP because the "(HTTP)" part of "Download (HTTP)" will
need to be removed too.
But let's see what users think first...
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.
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.
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.
I know it is somewhat useless, but I don't like them for
two reasons: first they cannot be seen, and I do not like things I
cannot see. Second, git highlights them, and this is disturbing...
I dislike tagging what I've recently edited, because I tend to
read what I intended to write, rather than what is there, aka
"marking my own homework". But I'll come back to divsvgm tomorrow
after the public book has rendered, and walk through the
instructions.
In the process, some attributes in single quotes have been changed to double
quotes, and a few attribute lists have been written on one line instead of
several lines.
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@24236 af4574ff-66df-0310-9fd7-8a98e5e911e0
Do not use let if result might be 0, which silently returns non-zero status
and can break scripts, or if result starts with 0 but is >7 e.g. 08, which
will be treated as octal and visibly report an error.
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@23513 af4574ff-66df-0310-9fd7-8a98e5e911e0
Fails to build with current poppler, and upstream has removed poppler for TL2021.
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@23505 af4574ff-66df-0310-9fd7-8a98e5e911e0
