> On 23 Nov 2023, at 11:14, Marco Patzer <li...@homerow.info> wrote: > > On Thu, 23 Nov 2023 08:58:56 +0100 > Taco Hoekwater <t...@bittext.nl> wrote: > >>> probably a side effect if moving some more to the (ntg) server in >>> the netherlands (also setting up the build there) >> >> Even if it used the right certificate, it would not work right now >> because of the move: there is nothing behind the connection. > > I used that server to check for the latest context version. What's > the recommended way to check for the latest version? Basically the > output of the \contextversion command?
The command context —version gives the local installed version. Not sure whether there is a clean way to see if there is a remote newer update without actually doing an update. You can check the mailing list, all new releases by Hans are now reported on the ntg-context list, but that may be less convenient than an actual test. mtx-install.sh does not have a —dry-run or —upgradable switch, afaik. Personally, I just run “bash install.sh” when I suspect there is a relevant update (install.sh is in the top-level context installation directory). Best wishes, Taco ___________________________________________________________________________________ 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 ___________________________________________________________________________________
