From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Update overwrites configuration
Date: Tue, 25 Feb 2014 04:23:57 +0100 [thread overview]
Message-ID: <CALBOmsbq3VRr26BXhg3nLY6y5fTH5gp5oe+Kj4pwC0rn=wR0fw@mail.gmail.com> (raw)
In-Reply-To: <CAANrE7qXBxaZF0cDp8FuwFXOKr0BFP+0MdbQc7SQYu8QqeE3CQ@mail.gmail.com>
On Tue, Feb 25, 2014 at 3:55 AM, Thangalin wrote:
> Hi,
>
> 1. Edit .../tex/texmf/web2c/texmfcnf.lua
> 2. Set TEXMFCACHE = "/var/cache/context/texmf-cache"
> 3. Run first-setup.sh to update ConTeXt.
Create a file texmfcnf.lua next to setuptex for example (that is: in
root of the installation) and set the variable there.
That is:
return {
content = {
variables = {
TEXMFCACHE = "/var/cache/context/texmf-cache",
},
},
}
> Expected Results
> TEXMFCACHE remains "/var/cache/context/texmf-cache"
>
> Actual Results
> TEXMFCACHE reverts to "$SELFAUTOPARENT/texmf-cache"
No, reverting to the original value is expected. If you want to modify
some variables, just place texmfcnf.lua (or texmf.cnf) somewhere else
and only put the differences there. The allowed locations for
texmfcnf.lua are determined by the variable TEXMFCNF being set in
texk/kpathsea/texmf.cnf in luatex sources:
TEXMFCNF = {\
$SELFAUTOLOC,\
$SELFAUTOLOC/share/texmf-local/web2c,\
$SELFAUTOLOC/share/texmf-dist/web2c,\
$SELFAUTOLOC/share/texmf/web2c,\
$SELFAUTOLOC/texmf-local/web2c,\
$SELFAUTOLOC/texmf-dist/web2c,\
$SELFAUTOLOC/texmf/web2c,\
\
$SELFAUTODIR,\
$SELFAUTODIR/share/texmf-local/web2c,\
$SELFAUTODIR/share/texmf-dist/web2c,\
$SELFAUTODIR/share/texmf/web2c,\
$SELFAUTODIR/texmf-local/web2c,\
$SELFAUTODIR/texmf-dist/web2c,\
$SELFAUTODIR/texmf/web2c,\
\
$SELFAUTOGRANDPARENT/texmf-local/web2c,\
$SELFAUTOPARENT,\
\
$SELFAUTOPARENT/share/texmf-local/web2c,\
$SELFAUTOPARENT/share/texmf-dist/web2c,\
$SELFAUTOPARENT/share/texmf/web2c,\
$SELFAUTOPARENT/texmf-local/web2c,\
$SELFAUTOPARENT/texmf-dist/web2c,\
$SELFAUTOPARENT/texmf/web2c\
}
> (c) user should be prompted to overwrite changed configuration values;
> (d) user should be prompted to accept overwriting each new value; or
> (e) a backup of the configuration file should be made, followed by a
> message that the changes have been overwritten and previous values
> archived.
No changes that you make to texmf/, texmf-context/, texmf-modules/ or
texmf-yourplatform/ will ever be preserved. You need to use other
texmf trees for that (like texmf-local for example).
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:[~2014-02-25 3:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 2:55 Thangalin
2014-02-25 3:23 ` Mojca Miklavec [this message]
2014-02-25 6:53 ` Thangalin
2014-02-25 10:49 ` Mojca Miklavec
2014-02-26 20:46 ` Thangalin
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='CALBOmsbq3VRr26BXhg3nLY6y5fTH5gp5oe+Kj4pwC0rn=wR0fw@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).