From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: RE : upload
Date: Wed, 25 Nov 2020 16:48:28 +0100 [thread overview]
Message-ID: <b2a4f7c8-c52b-5bb5-efa0-59c6d02f09a7@gmx.es> (raw)
In-Reply-To: <3a4c8954-3d37-3620-f2e3-6117ed71acd8@klankschap.nl>
On 11/24/20 7:22 PM, Floris van Manen wrote:
> On 24/11/2020 18:28, Pablo Rodriguez wrote:
>> I’m afraid you are getting an old version, since the newer one reads:
>>
>> mtx-context | ConTeXt Process Management 1.04
>> mtx-context |
>> mtx-context | main context file:
>> /home/ousia/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
>> mtx-context | current version: 2020.11.24 00:41
>> mtx-context | main context file:
>> /home/ousia/context/tex/texmf-context/tex/context/base/mkxl/context.mkxl
>> mtx-context | current version: 2020.11.24 00:41
>
> Well I can see that there is two versions.
Hi Floris,
the two versions you see are related to the code split mentioned by Hans
(my guess).
MkXL is now independent from MkIV. The version is the same, but there
are two codebases in the same distribution.
Think of it as MkII and MkIV contained in ConTeXt Standalone.
> But when unzipping the new context-linux-64.zip (nov 24 00:24)
> then run the install script
> sh ./install.sh
> will not solve the issue...
You shouldn’t need to download context-linux-64.zip.
Running install.sh on Linux should work fine again. No need to remove
tex/texmf-*.tma, either.
> So context is not working anymore.
> Any hints?
Just out of curiosity, could you fix your already installed ConTeXt version?
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-11-25 15:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 17:55 upload Hans Hagen
2020-11-23 18:28 ` upload Pablo Rodriguez
2020-11-23 18:29 ` upload Christian Prim
2020-11-23 19:21 ` upload Otared Kavian
2020-11-23 19:27 ` upload Hans Hagen
2020-11-23 19:24 ` upload Hans Hagen
2020-11-23 20:42 ` RE : upload Joseph
2020-11-23 22:02 ` Hans Hagen
2020-11-23 22:33 ` Floris van Manen
2020-11-24 17:28 ` Pablo Rodriguez
2020-11-24 18:22 ` Floris van Manen
2020-11-24 18:36 ` Floris van Manen
2020-11-25 15:48 ` Pablo Rodriguez [this message]
2020-11-25 17:15 ` Floris van Manen
2020-11-24 0:47 ` Rik Kabel
2020-11-24 1:04 ` 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=b2a4f7c8-c52b-5bb5-efa0-59c6d02f09a7@gmx.es \
--to=oinos@gmx.es \
--cc=ntg-context@ntg.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).