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.
