From: Jacob MacDonald <jaccarmac@gmail.com>
To: help-guix@gnu.org
Subject: Making mtxrun work with ConTeXt.
Date: Sun, 18 Oct 2020 20:43:37 -0500 [thread overview]
Message-ID: <CACy6W0Btsti7G1ST3fbGz3WVMKQ5rgSoWEcgMwncq+oF1y4F7w@mail.gmail.com> (raw)
Hopefully this is a quick question, as I've found a solution for the
immediate issue and hopefully for the long term as well. I wanted to
follow up on an old thread and see if my understanding of mtxrun is
correct.
I added the whole texlive distribution to my profile, built some
documents with pdflatex, and tried to compile a template which used
ConTeXt. It failed, unable to find the context.lua script. I tracked
down the file and set my TEXMF environment variable to
$GUIX_PROFILE/share/texmf-dist. This allowed mtxrun to work, but broke
pdflatex (pdflatex.fmt not found). This seems to be because the
scripts are in texmf-dist while the format files are in texmf-var. I
found one thread on this list about a similar issue from last year,
and the incoming changes to the texlive tree. Elsewhere on the
Internet, I found the suggestion that my mtxrun file database was out
of date.
Indeed, running mtxrun --generate (after unsetting TEXMF) seems to
solve my issue, allowing me to compile both documents without tweaking
environment variables. The generator seems to dump its index into
~/.texlive2019/
Is this a necessary step to use texlive-context-base on Guix? Or can
it somehow be rolled into the build/install process? If the answer is
yes, I can try my hand at a patch.
Thanks,
Jacob.
Thread in question:
https://lists.gnu.org/archive/html/help-guix/2019-08/msg00020.html
next reply other threads:[~2020-10-19 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 1:43 Jacob MacDonald [this message]
2020-10-19 21:28 ` Making mtxrun work with ConTeXt Jacob MacDonald
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACy6W0Btsti7G1ST3fbGz3WVMKQ5rgSoWEcgMwncq+oF1y4F7w@mail.gmail.com \
--to=jaccarmac@gmail.com \
--cc=help-guix@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).