From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: possible problem with setuptex
Date: Fri, 12 Jun 2009 10:35:26 +0200 [thread overview]
Message-ID: <6faad9f00906120135w23997e24l96beb8a2599f7eb9@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0906120717430.4379@gaston.couberia.bzh>
On Fri, Jun 12, 2009 at 07:25, Peter Münster wrote:
> On Fri, 12 Jun 2009, Mojca Miklavec wrote:
>
>> I left TEXMFCACHE variable as an excuse for not adding texmfcnf.lua to
>> the distribution. (Though in theory it's still not needed, you just
>> need to regenerate the database since LuaTeX doesn't know about the
>> location of your old cache.)
>>
>> I have added the file now.
>
> Great, it works now. Clean solution!
>
> But I'm asking myself, how SELFAUTOPARENT works:
> luatex is here: /opt/context/tex/texmf-linux-64/bin/luatex
> So it seems, that SELFAUTOPARENT is /opt/context/tex
Yes.
> But I would have guessed that it's /opt/context/tex/texmf-linux-64 ...
No, that's SELFAUTODIR.
> I even suggest, to suppress setuptex and only write in the readme/wiki,
> that the PATH must be adjusted so that context can be found, that's all.
We could issue a warning or we could put something at the end of
first-setup.sh (that needs to be renamed anyway) to tell users that
they should either adjust path or use the script.
I might be having weird habits, but I really like being able to have a
simple single command that switches the TeX tree.
export PATH=/something/very/long/:$PATH costs more effort to type than
just ". setuptex" :) :) :)
Wiki could/should be modified for sure. One day I need to revise all
kinds of instructions for different installations ... (finishing study
in time has a high priority at the moment).
The initial idea of setuptex was to shield all the environmental
variables that have been set by tetex. I suspect that cleaning up
setuptex had a consequence that it's not able to shield tetex any
more, but nobody has complained so far ...
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-06-12 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 10:26 Hans van der Meer
2009-06-11 10:47 ` Hans Hagen
2009-06-11 11:03 ` Peter Münster
2009-06-11 18:24 ` Mojca Miklavec
2009-06-11 21:25 ` Peter Münster
2009-06-11 22:45 ` Mojca Miklavec
2009-06-12 5:25 ` Peter Münster
2009-06-12 8:35 ` Mojca Miklavec [this message]
2009-06-12 8:50 ` Taco Hoekwater
2009-06-11 18:21 ` Mojca Miklavec
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=6faad9f00906120135w23997e24l96beb8a2599f7eb9@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).