From: Gour <gour@gour-nitai.com>
To: ntg-context@ntg.nl
Subject: Re: updating Minimals for MKIV
Date: Sat, 23 Jan 2010 08:52:17 +0100 [thread overview]
Message-ID: <20100123085217.5c4db4c7@gaura-nitai.no-ip.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1001221336310.22014@ybpnyubfg.ybpnyqbznva>
[-- Attachment #1.1: Type: text/plain, Size: 1414 bytes --]
On Fri, 22 Jan 2010 13:53:11 -0500 (EST)
>>>>>> "Aditya" == Aditya Mahajan <adityam@umich.edu> wrote:
Aditya> This is the best compromise I could get for running MkIV in a
Aditya> multi-user environment. I do not ask the mtx-update script to
Aditya> generate the formats (the --make flag is missing), because this
Aditya> script is running as root. Generating the formats means that
Aditya> luatex-cache will be generated by root, and then a user will
Aditya> never be able to writing anything in the cache directory. So, I
Aditya> do not generate the formats during the update.
Thank you for explanation.
Aditya> I generate the pdftex and xetex formats, and ask the user to
Aditya> run luatools --generate. When run for the first time, luatools
Aditya> --generate creates the $TEXMFCACHE directory. Since the command
Aditya> is run by the user, TEXMFCACHE is writable by the user.
Ahh, cool.
Aditya> Once luatools --generate is run, you can simply run "context
Aditya> filename". ConTeXt sees that the formats are wrong and
Aditya> regenerates them on the fly. The first luatools --generate is
Aditya> needed so that mtxrun can find the mtx-context script. (context
Aditya> is just a wrapper around mtx-context.lua).
Interesting...
Sincerely,
Gour
--
Gour | Hlapicina, Croatia | GPG key: F96FF5F6
----------------------------------------------------------------
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-01-23 7:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 11:14 Gour
2010-01-22 11:59 ` Hans Hagen
2010-01-22 13:17 ` Gour
2010-01-22 13:50 ` Gour
2010-01-22 13:52 ` Gour
2010-01-22 18:53 ` Aditya Mahajan
2010-01-22 19:40 ` Aditya Mahajan
2010-01-23 8:06 ` Gour
2010-01-23 18:17 ` Aditya Mahajan
2010-01-23 20:47 ` Gour
2010-01-24 20:54 ` Aditya Mahajan
2010-01-25 11:41 ` Gour
2010-01-23 7:52 ` Gour [this message]
2010-01-22 13:01 ` Mojca Miklavec
2010-01-22 13:22 ` Gour
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=20100123085217.5c4db4c7@gaura-nitai.no-ip.org \
--to=gour@gour-nitai.com \
--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).