From: tlaronde@polynum.com
To: 9front@9front.org
Subject: kerTeX: LaTeX update---and rough times coming
Date: Mon, 12 Oct 2020 16:59:54 +0200 [thread overview]
Message-ID: <20201012145954.GA12237@polynum.com> (raw)
Once more seeing the logs, I saw that a Plan9/9front user installed
kerTeX and tried to install LaTeX.
To make explanations short, LaTeX published a new version the 1st
October, making an incompatible change: requesting PDF primitives,
present in so-called "modern" engines (half of them have ceased
development years ago, while tex is still maintained by D.E. Knuth...),
but not present in TeX or e-TeX.
The problem is that these engines whether are programmed in C++ or draw
a bunch of libraries that depend on a compiler or on code not available
on Plan9 or others (but even with a C++ compiler, the
dependencies become a nightmare).
So, while I have designed the kerTeX packages to be simple scripts
downloading directly sources from CTAN and being quite independant from
the version (as long as the filenames for the unpacking procedure or the
dumping is unchanged, it works without needing changes with the updated
sources), I have now retrieved the latest compatible version, the
one from 2020-02-02 (PL5 BTW), and the package installs this one
served from my kergis.com server and not from CTAN (that doesn't know
about version; and instead of calling this LaTeX LaTeX3, it is still
identified as LaTeX2e while being incompatible).
I'm not a LaTeX user. So please, when something break specially with the
packages, it is likely I will not notice since I don't use them. But
then, just send me a message. I think I'm quite responsive...
Best,
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
http://www.kergis.com/kertex.html
http://www.sbfa.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
reply other threads:[~2020-10-12 14:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201012145954.GA12237@polynum.com \
--to=tlaronde@polynum.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).