Problems with texmf.cnf settings
Hi Hans! Hi Taco! Hi all! I am slowly getting at it. Don't ask me why, but now On Di, 25 Sep 2007, Hans Hagen wrote:
export TEMXFCNF=/usr/share/texmf/web2c
and calling luatools --verbose --generate did work, well, sort of. All
the cache files were generated in ~/luatex-cache.
There is only ONE BIG PROBLEM:
$ grep ^TEXMFDIST /usr/share/texmf/web2c/texmf.cnf
TEXMFDIST = /usr/share/texmf-{texlive,tetex}
which leads to:
...
LuaTools | locating list of /usr/share/texmf-{texlive
LuaTools | locating list of tetex}
...
without brace expansion. This is bad.
I know TEXMFDIST should be ONE tree, but it CAN be a brace expanded
list. It works. Well, in kpathsea, but not in luatools. So most scripts
are not found.
Can this be fixed?
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining
On Sa, 29 Sep 2007, Norbert Preining wrote:
There is only ONE BIG PROBLEM: $ grep ^TEXMFDIST /usr/share/texmf/web2c/texmf.cnf TEXMFDIST = /usr/share/texmf-{texlive,tetex}
My question is still there, but I temporarly solved it (using two
different names).
Something else: I tried your example:
$ mtxrun --script font --list lmroman10
Error in lua file loading: cannot open : No such file or directory
You said there must be a LUAINPUTS settings, so I did:
$ export LUAINPUTS=/usr/share/texmf/scripts/context/lua//
but with the same effect.
Desperate as I am I did put the above LUAINPUTS line into the texmf.cnf,
called again the luatools --verbose --generate and then tried the mtxrun
call, again with the same effect.
How are you guys setting up your system??? Is this magic? Or is there
nobody else besides you two actually using/trying it out???
Thanks a lot for any suggestions!
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining
$ export LUAINPUTS=/usr/share/texmf/scripts/context/lua//
You might have to add a second directory (see http://www.ntg.nl/pipermail/ntg-context/2007/026272.html), but there is a much simpler way, see below:
Desperate as I am I did put the above LUAINPUTS line into the texmf.cnf,
This should not make any difference, so it's quite lucky that it doesn't ;-)
How are you guys setting up your system??? Is this magic? Or is there nobody else besides you two actually using/trying it out???
Download http://www.pragma-ade.com/context/install/linuxtex.zip (or whatever is appropriate for your system) and source setuptex. That's really all you have to do if you use the minimal ConTeXt distribution; and of course you can adapt it to suit your needs, just have a look at it. The first half of the script tries to identify the topmost directory of your installation with some simple heuristics (it calls it TEXROOT), and the other half then sets all necessary variables accordingly. Arthur
Hi Arthur, hi Hans, hi all! On Sa, 29 Sep 2007, Arthur Reutenauer wrote:
You might have to add a second directory (see http://www.ntg.nl/pipermail/ntg-context/2007/026272.html), but there is a much simpler way, see below:
Thanks, that was a good hint. So the problem is that the current setting in our texmf.cnf for LUAINPUTS is not enough. We have currently: LUAINPUTS = .;$TEXMF/scripts/{$progname,$engine,}/lua// but as far as I can see we need at least also: scripts/context/lua// tex/context/base// for luatools/mtxrun to work. It seems that mtxrun is not setting the $engine nor $progname settings, and the tex/context/base/ cannot be found anyway. Well to sum it up (what I need on Debian): 1) export TEXMFCNF=/usr/share/texmf/web2c 2) adjust LUAINPUTS to add the above two settings 3) call luatools --verbose --generate after this mtxrun --script fonts --list lmroman10 gives me: report >> fontnames: identifying tree font files with suffix otf report >> fontnames: 137 tree files identified, 421 hash entries added, runtime 1.65 seconds ... lmroman10-bold LMRoman10-Bold lmroman10-bold.otf ... lmroman10-unslanted LMRoman10-Unslanted lmroman10-unslanted.otf Now I will try to set things up so that normal Debian users get a working MkIV with luatex/context without *too* much manual interference. What still puzzles me, or better makes me a bit sceptic, is this luatex cache thingy, which needs updating at any time. I guess I have to add some magic to the "mktexlsr" script that in case that luatex is installed it also calls luatools --generate ..., but I am not sure whether this is a good idea, needs definitely some testing.
Download http://www.pragma-ade.com/context/install/linuxtex.zip (or whatever is appropriate for your system) and source setuptex. That's
This is not a solution, I am a system integrator, I want to get this
working for Debian, so I cannot rely on stuff to be downloaded etc. I
need to know *exactely* what is necessary, and have to develop a method
to make this working on all the Debian machines out there. Yup. But
thanks for the hint.
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining
What still puzzles me, or better makes me a bit sceptic, is this luatex cache thingy, which needs updating at any time.
I do not think that luatools --generate needs to be called more frequently than mktexlsr (it basically does the same job; the purpose of the whole thing is to replace kpathsea). Couldn't it be made a part of the post-install script?
This is not a solution, I am a system integrator, I want to get this working for Debian, so I cannot rely on stuff to be downloaded etc.
Sure, but *you* could download it and have a look at it. It's a hundred-line script and all it does is setting some variables. By the way, you can download the stand-alone script at http://minimals.contextgarden.net/minimals/linux/setuptex
I need to know *exactely* what is necessary, and have to develop a method to make this working on all the Debian machines out there.
I guess once you've set LUAINPUTS correctly, everything should run correctly but if you have other questions, you really should ask them on the ConTeXt list because it's not really about LuaTeX (and we already had the same sort of questions a bunch of times there). As a matter of fact, somebody there just reported that for him (on Windows) it was enough to set: PATH = G:\rsync\windows\texmf-mswin\bin; OSFONTDIR = %WINDIR%\Fonts TEXMF = {g:\rsync\windows\texmf,g:\rsync\windows\texmf-local} TEXMFCACHE = %WINDIR%\Temp TEXMFCNF = G:\rsync\windows\texmf{-local,}/web2c LUAINPUTS = .;$TEXMF/tex/context/base;$TEXMF/scripts/context/lua Arthur
participants (2)
-
Arthur Reutenauer -
Norbert Preining