ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: news3@nililand.de, Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: How to add a local texmf tree to context minimals?
Date: Thu, 24 Mar 2011 10:26:07 +0100	[thread overview]
Message-ID: <4D8B0E2F.8010206@wxs.nl> (raw)
In-Reply-To: <AANLkTikRXzN298nSFZOCrebP7EuOq+Y0mtecXwoEnqwG@mail.gmail.com>

On 24-3-2011 7:57, Mojca Miklavec wrote:
> On Wed, Mar 23, 2011 at 20:08, Ulrike Fischer wrote:
>>
>> At second I want actually to add more than one tree ;-)
>>
>> My main problem is that there quite a lot of configuration files
>> which look like good candidates (I found texmf.cnf, texmfcnf.lua,
>> context.cnt, contextcnf.lua.) and that I don't know where to put a
>> local version which will not be changed by updates.
>
> texmf.cnf is for MKII and texmfcnf.lua is for MKIV. The files
> context.cnf and contextcnf.lua are not used. They are usually just the
> source for texmf.cnf and texmfcnf.lua, but they are not taken
> automatically.
>
> One way is to set environmental variables, but probably a better way
> is to create a copy of texmf.cnf&  texmfcnf.lua in texmf-local/web2c/
> and change the TEXMF variable there. No, wait. texmf-local is not
> known until texmf.cnf is actually read in (chicked-and-egg problem).

Did you test it?

Just put a cnf there and run

mtxrun --configurations

and see what gets reported. Here I have one in the local tree because I 
need to hook in my dev paths.

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2011-03-24  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 18:31 Ulrike Fischer
2011-03-23 18:47 ` Hans van der Meer
2011-03-23 19:08   ` Ulrike Fischer
2011-03-24  6:57     ` Mojca Miklavec
2011-03-24  9:26       ` Hans Hagen [this message]
2011-03-24  9:39       ` Ulrike Fischer
2011-03-24  9:45         ` Mojca Miklavec
2011-03-24 10:08           ` Ulrike Fischer
2011-03-24 13:01             ` Mojca Miklavec
2011-03-23 22:13 ` Hans Hagen
2011-03-23 22:30   ` Aditya Mahajan
2011-03-23 23:16     ` Hans Hagen

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=4D8B0E2F.8010206@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=mojca.miklavec.lists@gmail.com \
    --cc=news3@nililand.de \
    --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).