From: Alan Braslau via ntg-context <ntg-context@ntg.nl>
To: Alan Braslau via ntg-context <ntg-context@ntg.nl>
Cc: Alan Braslau <alan.braslau@icloud.com>
Subject: Re: Trouble with latest...
Date: Tue, 10 Jan 2023 16:17:12 -0700 [thread overview]
Message-ID: <20230110161712.3bea3559@boo.my.domain> (raw)
In-Reply-To: <20230109190854.15e7989a@boo.my.domain>
On Mon, 9 Jan 2023 19:08:54 -0700
Alan Braslau via ntg-context <ntg-context@ntg.nl> wrote:
> On Mon, 9 Jan 2023 18:40:08 +0100
> Alain Delmotte via ntg-context <ntg-context@ntg.nl> wrote:
>
> > Anytime a new upload is announced, I download the
> > context-win64.zip unpack it and run install.bat and setpath.bat.
> >
> > Is it a fresh installation? Or should I from time to time
> > erase my installation and run install.bat to create a new
> > distribution?
>
> This is not a *fresh* install. In fact, you can simply run
> ./install.bat - there is no need to download context-win64.zip.
>
> Having said that, the latest problem with the update has to do with an
> updated luametatex binary, so your method might have worked by
> updating the binary with the unzip, even if it is not a "fresh"
> install.
For information:
I tried updating by downloading a fresh zip and unpacking it over an
existing installation, then running ./install.bat. This failed with the
latest upload, although unzipping to a new location and running
./install.bat resulting in a good, updated distribution.
The install/update and mtxrun scripts could possibly be improved to
1. start by updating the luametatex binary in a first step,
then rerunning to update the rest of the distribution;
2. systematically clear the luametatex-cache upon update (I
believe that this is a small price to pay for robustness).
However, such changes clearly are not a priority to work out, for now.
Alan
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2023-01-10 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 19:02 Thomas A. Schmitz via ntg-context
2023-01-08 20:02 ` Wolfgang Schuster via ntg-context
2023-01-08 20:32 ` Thomas A. Schmitz via ntg-context
2023-01-08 20:37 ` Hans Hagen via ntg-context
2023-01-09 17:40 ` Alain Delmotte via ntg-context
2023-01-10 2:08 ` Alan Braslau via ntg-context
2023-01-10 23:17 ` Alan Braslau via ntg-context [this message]
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=20230110161712.3bea3559@boo.my.domain \
--to=ntg-context@ntg.nl \
--cc=alan.braslau@icloud.com \
/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).