From: "Rainer J.H. Brandt via ntg-context" <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Rainer J.H. Brandt" <rjhb@bb-c.de>
Subject: Re: problem with MkIV/TeXlive/TEXMFCACHE
Date: Mon, 30 Aug 2021 16:55:35 +0200 [thread overview]
Message-ID: <24876.61799.293374.646961@mail.bb-c.de> (raw)
In-Reply-To: <nycvar.YAK.7.78.908.2108300915330.398836@nqv-guvaxcnq>
Aditya Mahajan via ntg-context writes:
> On Mon, 30 Aug 2021, Rainer J.H. Brandt via ntg-context wrote:
>
> > But, as I said, my texmf.cnf sets TEXMFCACHE to $TEXMFSYSVAR;$TEXMFVAR,
> > and TEXMFSYSVAR is /var/opt/texlive. Why is that ignored?
>
> mtxrun (and context MKIV and LMTX) do not read texmf.cnf rather read values from contextcnf.lua (it used to be texmfcnf.lua, not sure how TL handles this).
Thanks a lot. That put me on the right track. I see that this file is
mentioned on the wiki, but I hadn't recognized its importance.
I have found and edited texmfcnf.lua, and made progress.
> You can also try setting it explicitly in the shell:
>
> $ TEXMFCACHE=/var/opt/texlive/texmf-cache mtxrun --generate
I tried to avoid that, and thanks to your pointer above, won't need that.
However, I'm still not completely happy: I've set TEXMFCACHE to contain
/var/opt/texlive first and then also an individual directory under $HOME.
When I run context under my personal account, it only uses the second.
I assume that's because I may not write under the first. There's a comment
in texmfcnf.lua about that.
Does it perhaps make no sense at all to have a system-wide luatex-cache?
Thank you,
Rainer
___________________________________________________________________________________
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:[~2021-08-30 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 8:25 Rainer J.H. Brandt via ntg-context
2021-08-27 15:57 ` luigi scarso via ntg-context
2021-08-30 9:49 ` Rainer J.H. Brandt via ntg-context
2021-08-30 10:22 ` luigi scarso via ntg-context
2021-08-30 10:48 ` Rainer J.H. Brandt via ntg-context
2021-08-30 12:32 ` Arthur Rosendahl via ntg-context
2021-08-30 14:41 ` Rainer J.H. Brandt via ntg-context
2021-08-30 13:18 ` Aditya Mahajan via ntg-context
2021-08-30 14:55 ` Rainer J.H. Brandt via ntg-context [this message]
2021-08-30 14:33 ` luigi scarso via ntg-context
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=24876.61799.293374.646961@mail.bb-c.de \
--to=ntg-context@ntg.nl \
--cc=rjhb@bb-c.de \
/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).