From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: vm via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: [NTG-context] [ update message ]
Date: Sun, 7 May 2023 16:05:18 +0200 [thread overview]
Message-ID: <fee04a6e-f8e4-1892-8489-a2c524e3a7cd@freedom.nl> (raw)
In-Reply-To: <bc0d9e94-2ce3-29dd-29ab-c9fa79a78b5d@klankschap.nl>
On 5/7/2023 3:18 PM, vm via ntg-context wrote:
> running the sh install.sh script to update to the latest version i get a
> message:
>
> /home/vm/context/tex/texmf-linux-64/bin/luatex: unrecognized option
> '--socket'
>
> there is probably a reason for it, context seems to compile just fine.
ah, ok, so that luatex update even broke the context updater (i didn't
realize that luatex would quit on an unknown option instead of just
ignoring it)
anyway, as there is no way we can deal with such incompatible updates
out of our control, one can install lmtx which should be fine (and
likely has the right luatex too, or you can pick up some luatex from the
compile farm which should work ok with recent scripts)
summary:
- there is a luatex update that breaks context but is needed for other
macro packages, and in principle such a fundamental incompatinility
should go along with a context update
- the update therefore needs a patched mtxrun although one never patches
mtxrun directly unless doing that off-context-zip (it's now how mtxrun
is created)
- the luat-fmt is the one that should get two "--socket" snippets
because otherwise a context run can fail in some scenarios
- new observation: older engines might fail with new scripts but I'm not
going to check for versions (in fact, if we weren't aware of the issue
contexts would fail everywhere once such an update rolls out)
So .. not much we can do about it other than just manually adapt when a
situation arises. The good news is that luametatex is unaffected and
that is what the majority used.
Hans
ps. I assume new luatex binaries have to be put into the old mkiv/mkii
installers when they ship with a newer script. Kind of a mess.
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-05-07 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 13:18 vm via ntg-context
2023-05-07 14:05 ` Hans Hagen via ntg-context [this message]
2023-05-07 14:47 ` luigi scarso via ntg-context
2023-05-07 14:57 ` Hans Hagen via ntg-context
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=fee04a6e-f8e4-1892-8489-a2c524e3a7cd@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.nl \
/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).