From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: updating Minimals for MKIV
Date: Fri, 22 Jan 2010 14:01:33 +0100 [thread overview]
Message-ID: <6faad9f01001220501x24d0b29csa784f74a0e971e22@mail.gmail.com> (raw)
In-Reply-To: <20100122121417.6a4114c8@gaura-nitai.no-ip.org>
On Fri, Jan 22, 2010 at 12:14, Gour wrote:
> Hiya!
>
> * For making MKIV format
>
> luatools --selfupdate
> mtxrun --selfupdate
--selfupdate is meant for you to be on the safe side. Update mechanism
should now update these two files, so it should not be really needed.
> luatools --generate
> context --make
luatools --generate is definitely needed on fresh install (it should
be done automatically, but it isn't for some weird md5-related reason
I suppose).
Once you have mkiv working, the "context --make" is executed
automatically in case that formts don't match.
> while the package for Archlinux has the following update function:
>
> post_upgrade() {
> source /opt/context-minimals/setuptex
> mktexlsr
> texexec --make cont-en metafun
> texexec --make --xetex
This is needed for mkii only.
> echo "*************************************************************"
> echo "To use ConTeXt minimals run"
> echo " /opt/context-minimals/setuptex"
> echo "To use MkIV run"
> echo " luatools --generate"
> echo "*************************************************************"
> }
>
>
> i.e. only "luatools --generate".
>
> Anyone can clarify?
I guess that's because mkiv generates new formats automatically (I'm
not sure if it also calls luatools --generate in that case, but it
could if it doesn't).
Mojca
___________________________________________________________________________________
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-22 13:01 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
2010-01-22 13:01 ` Mojca Miklavec [this message]
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=6faad9f01001220501x24d0b29csa784f74a0e971e22@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.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).