From: Aditya Mahajan <adityam@umich.edu>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: name of cache used by mkiv and lmtx
Date: Sun, 7 Apr 2019 13:04:30 -0400 (EDT) [thread overview]
Message-ID: <nycvar.YAK.7.76.44.1904071302390.26861@nqv-guvaxcnq> (raw)
In-Reply-To: <af14208d-09f5-6296-5336-d1ae394eeb5d@xs4all.nl>
On Sun, 7 Apr 2019, Hans Hagen wrote:
> On 4/6/2019 8:49 PM, Aditya Mahajan wrote:
>> On Sat, 6 Apr 2019, Alan Braslau wrote:
>>
>>> On Sat, 6 Apr 2019 13:46:57 -0400 (EDT)
>>> Aditya Mahajan <adityam@umich.edu> wrote:
>>>
>>>> Is there a way to avoid that? I can, of course, set different values of
>>>> TEXMFCACHE for both distributions, but does it make sense to to use a
>>>> different hash (5fe67e...) for the two?
>>>
>>> Why do you set TEXMFCACHE
>>> and not simply keep separate texmf-cache directories
>>> under your lmtx and mkiv CONTEXTROOT directories?
>>
>> I install both mkiv and lmtx at /opt/... so that the installations can be
>> shared by multiple users. TEXMFCACHE needs to be writable by the user, so
>> the natural choice is to set TEXMFCACHE to $HOME/texmf-cache.
>
> We only make an engine distinction (luatex luajittex luametatex) in the
> format file not in the cache and that is because the formats can differ but
> in other places the suffix makes the difference
>
> doing that in the cache in possible but in the end i don't expect one
> installation to have both engines because then we might that granularity in
> more places
Ok.
> we have tma tmc (lua) tmb (jit) ... one option is to use tmd (or so) for
> luametatex but for that we need to adapt some lua code
There is really no need to introduce more complexity into the code. As I
said, it is straight forward for me to use different cache directories for
mkiv and lmtx.
Thanks,
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2019-04-07 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 17:46 Aditya Mahajan
2019-04-06 18:20 ` Alan Braslau
2019-04-06 18:49 ` Aditya Mahajan
2019-04-07 13:06 ` Hans Hagen
2019-04-07 17:04 ` Aditya Mahajan [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=nycvar.YAK.7.76.44.1904071302390.26861@nqv-guvaxcnq \
--to=adityam@umich.edu \
--cc=j.hagen@xs4all.nl \
--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).