ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: updating Minimals for MKIV
Date: Fri, 22 Jan 2010 13:53:11 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.01.1001221336310.22014@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <20100122145255.42e5cd08@gaura-nitai.no-ip.org>

On Fri, 22 Jan 2010, Gour wrote:

> On Fri, 22 Jan 2010 12:59:39 +0100
>>>>>>> "Hans" == Hans Hagen <pragma@wxs.nl> wrote:
>
> Hans> if you download the minimals installer script from the garden and
> Hans> run
> Hans>
> Hans>    ./first-update.sh --engine=luatex
>
> Hmm, the build script does not run first-update.sh but it invokes the
> following:
>
> ...
> msg "Starting download or update of ConTeXt distribution"
> $srcdir/bin/texlua $srcdir/bin/mtxrun --script
> $srcdir/bin/mtx-update.lua  \ --platform=$_platform
> --texroot=$srcdir/tex --engine=all --extras=all \ --context=beta
> --update  --force || return 1
>
> Maybe I should wait for Aditya to explain what is he doing...

This is the best compromise I could get for running MkIV in a multi-user 
environment. I do not ask the mtx-update script to generate the formats 
(the --make flag is missing), because this script is running as root. 
Generating the formats means that luatex-cache will be generated by root, 
and then a user will never be able to writing anything in the cache directory.
So, I do not generate the formats during the update.  In the post-install

> post_install() {
>  source /opt/context-minimals/setuptex
>  mktexlsr
>  texexec --make cont-en metafun
>  texexec --make --xetex
>  echo "*************************************************************"
>  echo "To use ConTeXt minimals run"
>  echo ". /opt/context-minimals/setuptex"
>  echo "To use MkIV run"
>  echo "luatools --generate"
>  echo "*************************************************************"
> }


I generate the pdftex and xetex formats, and ask the user to run luatools
--generate. When run for the first time, luatools --generate creates the
$TEXMFCACHE directory. Since the command is run by the user, TEXMFCACHE is
writable by the user.

Once luatools --generate is run, you can simply run "context filename". ConTeXt
sees that the formats are wrong and regenerates them on the fly. The first
luatools --generate is needed so that mtxrun can find the mtx-context script.
(context is just a wrapper around mtx-context.lua).

Currently something is going wrong in the installation script. Others have said
that you need to "press enter twice" to get it to run. My guess is that
something is trying to generate the luatools format, even though I have not
asked for it. I will investigate further why this is happening.

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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2010-01-22 18:53 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 [this message]
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
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=alpine.LNX.2.01.1001221336310.22014@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --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).