From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: [NTG-context] update
Date: Thu, 27 Apr 2023 09:38:02 +0200 [thread overview]
Message-ID: <1018aaf6-9063-79b5-2a15-710dc6c97879@xs4all.nl> (raw)
In-Reply-To: <86867317c1f1d63323755f4981ad5a7a@polarcom.com>
On 4/27/2023 2:50 AM, lynx--- via ntg-context wrote:
> Re: performing update(s)
>
> 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 ?
Basically tex live is the yearly snapshot. I actually dont' know the
rules for updating texlive but there are definitely updates. But as much
relates there (like engines shared between macro packages) it can be
that only macros get updated and not engines (also relates to multiple
platforms) so fundamental changes to luatex as engine .. hard to predict.
But you can just install the lmtx installation alongside (it's small
compared to tex live) and have the best of both worlds. The lmtx
installation also has mkiv. It also comes with the fonts that match what
we expect in context (as fonts get updated or changed).
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
___________________________________________________________________________________
next prev parent reply other threads:[~2023-04-27 7:38 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
2023-04-27 7:38 ` Hans Hagen via ntg-context [this message]
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=1018aaf6-9063-79b5-2a15-710dc6c97879@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).