From: Max Chernoff via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Max Chernoff <tex@maxchernoff.ca>
Subject: [NTG-context] Re: upload
Date: Sat, 14 Jun 2025 00:47:15 -0600 [thread overview]
Message-ID: <4e4de5b03889f8cc1a8a0982a3ef4db347bbb37f.camel@maxchernoff.ca> (raw)
In-Reply-To: <d91a8a34-3870-43c1-abfd-5098a7e99a71@xs4all.nl>
Hi Hans,
On Thu, 2025-06-12 at 13:56 +0200, Hans Hagen wrote:
> I uploaded a new version,
Looks like my autoupdating scripts worked well, the new version should
be available in TeX Live as of a few hours ago.
In case anyone ever encounters any critical bugs in the version packaged
by TeX Live, it's pretty easy to downgrade the prior version:
$ tlmgr restore context 75454
$ tlmgr restore context.x86_64-linux 75425
(run "tlmgr restore context" to list the available versions)
Or if you need to downgrade to an even earlier version, it's only
slightly more involved:
$ rm /usr/local/texlive/2025/bin/x86_64-linux/{mtxrun,mtxrun.lua,context,context.lua,luametatex}
$ tlmgr install --reinstall --file \
https://texlive.info/tlnet-archive/2025/06/12/tlnet/archive/context.tar.xz \
https://texlive.info/tlnet-archive/2025/06/12/tlnet/archive/context.x86_64-linux.tar.xz
(replace the "2025/06/12" with whatever date you want to downgrade to)
> -- additional warnings (or abort) in case one runs from tex live and
> missing or expected files
Sure, fine by me. One possible idea: instead of relying on the file
luametatex.h existing/not existing, I could add a "distributed_by" key
(or similar) to the texmfcnf.lua file in TeX Live. Then ConTeXt could
display the contents of that key in the log file, right below the
ConTeXt version, so that it's clear to users (and people reading
messages to the mailing list) that they're using an unofficial version.
> ps. i might reintroduce the beta/current updating scheme at some point
> .. still undecided
Also fine by me; let me know if you ever want me to make any changes to
the packaging in TeX Live.
> % texmf-dist/tex/context/modules/mkxl/m-texlive.mkxl
> %D This is a variant on code I found in a \TEXLIVE\ installation in \type
> %D {cont-sys.mkxl} in 2025. In \type {cont-sys.mkxl} one can add this:
> %D
> %D \starttyping
> %D \usemodule[texlive]
> %D \stoptyping
I've updated cont-sys.mkxl with your new code, thanks!
> %D I guess that the reason for this hackery is that a \TEXLIVE\ doesn't do
> %D an update of the file database after installing some \CONTEXT\ related
> %D files. In a similar manner, when a used updated something \CONTEXT\ we
> %D don't generate an lsr file. Here both are checked.
So TeX Live (tlmgr) always runs "mtxrun [--luatex] --generate" and
"context [--luatex] --make" whenever it modifies any ConTeXt files, but
since most users install TeX Live to "/usr/local/texlive/$YEAR" (or
similar), tlmgr runs as root, so it can only update the caches/formats
in "/usr/local/texlive/$YEAR/texmf-var/". But if a someone ever runs
"mtxrun --generate" or "context --make" as a regular user, ConTeXt will
create caches/formats in "~/.texlive$YEAR/texmf-var/", and then it will
ignore all the files in "/usr/local/texlive/$YEAR/texmf-var/", even if
they're newer than the user-local ones.
I wrote that code as a quick hack back in 2023, but as we all know,
quick hacks tend to stay around far longer than they should :). If
there's some way to tell ConTeXt to always use the system's filename
cache files for "root == 'selfautoparent:texmf-dist'", and then the
user-local filename cache files for other roots, that would probably be
even better.
Thanks again,
-- Max
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next parent reply other threads:[~2025-06-14 6:59 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d91a8a34-3870-43c1-abfd-5098a7e99a71@xs4all.nl>
2025-06-14 6:47 ` Max Chernoff via ntg-context [this message]
2025-06-14 7:41 ` Hans Hagen
2025-06-14 8:47 ` Max Chernoff via ntg-context
2025-06-14 9:45 ` Hans Hagen
2025-06-14 10:24 ` Max Chernoff via ntg-context
2025-02-12 11:05 [NTG-context] upload Hans Hagen
2025-02-12 14:48 ` [NTG-context] upload Steffen Wolfrum
2025-02-12 15:13 ` Hans Hagen via ntg-context
2025-02-13 14:28 ` Steffen Wolfrum
2025-02-13 16:37 ` Hans Hagen
2025-02-14 10:36 ` Steffen Wolfrum
2025-02-14 10:57 ` Steffen Wolfrum
2025-02-14 15:50 ` Pablo Rodriguez via ntg-context
2025-02-14 16:13 ` Hans Hagen
2025-02-14 17:05 ` Pablo Rodriguez via ntg-context
2025-02-14 18:18 ` Hans Hagen
2025-02-15 13:10 ` Pablo Rodriguez via ntg-context
2025-02-14 10:58 ` Hans Hagen
2025-02-14 11:29 ` Steffen Wolfrum
2025-02-14 12:26 ` Hans Hagen
2025-02-14 19:03 ` Steffen Wolfrum
2025-02-14 19:43 ` Hans Hagen
2025-02-15 19:07 ` Steffen Wolfrum
2025-04-29 11:12 ` Steffen Wolfrum
2025-04-29 14:38 ` Pablo Rodriguez via ntg-context
2025-02-15 13:16 ` Pablo Rodriguez via ntg-context
2025-02-15 18:29 ` Steffen Wolfrum
2025-02-16 9:03 ` Pablo Rodriguez via ntg-context
2025-02-16 10:09 ` Thomas Meyer
2025-02-16 10:36 ` Pablo Rodriguez via ntg-context
2025-02-16 10:57 ` Thomas Meyer
2025-02-16 11:02 ` Pablo Rodriguez via ntg-context
2025-02-16 11:09 ` Thomas Meyer
2025-02-18 12:02 ` Steffen Wolfrum
2025-02-18 16:19 ` Pablo Rodriguez via ntg-context
2025-02-19 6:22 ` Steffen Wolfrum
2025-02-21 11:32 ` Steffen Wolfrum
2025-02-25 16:01 ` Pablo Rodriguez via ntg-context
2025-02-28 11:44 ` Steffen Wolfrum
-- strict thread matches above, loose matches on Subject: below --
2024-09-17 11:52 [NTG-context] upload Hans Hagen
2024-09-17 20:12 ` [NTG-context] upload Henning Hraban Ramm
2024-09-18 18:12 ` Pablo Rodriguez via ntg-context
2024-09-18 18:28 ` Henning Hraban Ramm
2024-07-31 17:55 [NTG-context] upload Hans Hagen via ntg-context
2024-07-31 18:57 ` [NTG-context] upload Henning Hraban Ramm
2024-08-01 7:21 ` Henning Hraban Ramm
2024-08-01 7:44 ` Hans Hagen
2024-04-01 7:31 [NTG-context] upload Hans Hagen
2024-04-01 8:17 ` [NTG-context] upload Mikael Sundqvist
2024-04-01 9:34 ` Otared Kavian
2024-04-01 9:48 ` Hans Hagen
2024-02-14 12:44 [NTG-context] upload Hans Hagen
2024-02-15 9:02 ` [NTG-context] upload luigi scarso
2024-02-15 9:35 ` Mikael Sundqvist
2024-02-15 9:48 ` Hans Hagen
2024-01-17 23:13 [NTG-context] upload Hans Hagen
2024-01-18 1:35 ` [NTG-context] upload Otared Kavian
2024-01-18 6:29 ` Mikael Sundqvist
2024-01-18 7:17 ` Jeong Dal via ntg-context
2024-01-18 14:27 ` Otared Kavian
2024-01-18 14:49 ` Hans Hagen
2024-01-18 19:04 ` Alain Delmotte
2024-01-18 19:43 ` Denis Maier via ntg-context
2024-01-19 17:34 ` Pablo Rodriguez via ntg-context
2024-01-19 18:55 ` Denis Maier via ntg-context
2024-01-19 21:56 ` Otared Kavian
2024-01-20 7:41 ` Alain Delmotte
2024-01-20 8:38 ` Hans Hagen via ntg-context
2024-01-20 8:58 ` vm via ntg-context
2024-01-20 9:32 ` Ursula Hermann
2024-01-20 9:45 ` Hans Hagen
2024-01-23 9:09 ` Hans Hagen via ntg-context
2024-01-23 16:29 ` Otared Kavian
2024-01-23 18:02 ` Bruce Horrocks
2024-01-23 20:08 ` Hans van der Meer via ntg-context
2024-01-23 20:59 ` Otared Kavian
2024-01-23 21:06 ` Thomas A. Schmitz
2024-01-24 9:29 ` Otared Kavian
2024-01-23 21:02 ` Otared Kavian
2024-01-20 13:04 ` Pablo Rodriguez via ntg-context
2024-01-21 11:33 ` Alain Delmotte
2023-08-09 15:42 [NTG-context] upload Hans Hagen
2023-08-09 19:29 ` [NTG-context] upload Rik Kabel
2023-08-09 21:11 ` Hans Hagen
2023-08-10 12:57 ` Henning Hraban Ramm
2023-08-10 13:03 ` Hans Hagen
2023-08-10 13:33 ` Henning Hraban Ramm
2023-08-10 13:52 ` Wolfgang Schuster
2023-08-10 14:41 ` Hans Hagen via ntg-context
2023-08-10 15:02 ` Wolfgang Schuster
2023-08-10 16:14 ` Henning Hraban Ramm
2023-08-11 1:31 ` Thangalin
2023-08-11 6:19 ` Hans Hagen
2023-08-11 16:41 ` Thangalin
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=4e4de5b03889f8cc1a8a0982a3ef4db347bbb37f.camel@maxchernoff.ca \
--to=ntg-context@ntg.nl \
--cc=tex@maxchernoff.ca \
/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).