ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Max Chernoff via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: [NTG-context] update
Date: Thu, 27 Apr 2023 09:58:56 +0200	[thread overview]
Message-ID: <5f61d47f-d3ec-5722-fd22-beb329993cef@freedom.nl> (raw)
In-Reply-To: <5f0cb79a1cd743c88d258f85bc8681850057aa58.camel@telus.net>

On 4/27/2023 7:11 AM, Max Chernoff via ntg-context wrote:
> Hi Lynx, Aditya,
> 
> 
>>> New to conTeXt, have not performed a specific update prior to this.
>>>
>>> My conTeXt installation is part of TeXlive-2023 (under Linux OS). Will
>>> the updates to ConTeXt be handled by tlmgr ?
>>
>> No. Usually, texlive updates context once a year.
> 
> This is correct in general, but this specific update *will* end up in
> TL2023 due to the engine changes that Hans mentioned. It's not in TL
> yet, but we're actively working on it, so it should show up within a
> week or so (hopefully).
Correction: Luigi and I are still discussing how to make it work because 
there is some init order issue and we want to be sure that context (and 
its scripts) keep working. It would be sort of weird if context (where 
luatex originates) would stop working as expected. Keep in mind that 
luatex is also a lua engine. and I assume that the texlive team also has 
some tests to perform (apart from getting all platforms updated which 
for some is more work, like apple signing).

The issue (disabling socket by default) is not that pressing as socket 
has been with us for right fromn the start) and security wise there are 
plenty ways tex can mess up your system if someone wants.

Hans


-----------------------------------------------------------------
                                           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
___________________________________________________________________________________

  reply	other threads:[~2023-04-27  7:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 21:55 Hans Hagen via ntg-context
2023-04-26 23:54 ` Jairo A. del Rio via ntg-context
2023-04-27  2:25   ` Rik Kabel via ntg-context
2023-04-27  2:34     ` Jairo A. del Rio via ntg-context
2023-04-27  7:52   ` Hans Hagen via ntg-context
2023-04-27  0:50 ` lynx--- via ntg-context
2023-04-27  1:52   ` Aditya Mahajan via ntg-context
2023-04-27  5:11     ` Max Chernoff via ntg-context
2023-04-27  7:58       ` Hans Hagen via ntg-context [this message]
2023-04-27  7:38   ` Hans Hagen via ntg-context
2023-04-27  8:32     ` Max Chernoff via ntg-context
2023-04-27 21:51       ` lynx--- via ntg-context
2023-04-27 23:54         ` Max Chernoff via ntg-context
2023-06-04 17:01 Hans Hagen via ntg-context
2024-01-08 10:36 Hans Hagen via ntg-context
2024-03-11 17:48 Hans Hagen

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=5f61d47f-d3ec-5722-fd22-beb329993cef@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).