From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: luatex on debian
Date: Fri, 12 Oct 2007 18:11:26 +0200 [thread overview]
Message-ID: <470F9CAE.20905@wxs.nl> (raw)
In-Reply-To: <22af238a0710120810i2784e502meef92f4f7aee9a9f@mail.gmail.com>
George N. White III wrote:
> debian (unstable,testing?) users can get a snapshot release of luatex in
> apt package form.
>
> This works for me, but there are a few things that needed slight adjustment, so
> I wanted to report them here to encourage others to start testing it.
>
> I needed to set TEXMF=/etc/texmf. Luatools doesn't seem to handle the {..}
> in the variables that are combined in TEXMF. Also, when it didn't find
hm, it should handle the {} ok (well, i did rewrite that part a bit
because it didn't handle some cases; can you send me the TEXMF spec that
failed?)
> AlProTex.sty, the message indicated that it couldn't find AlProTeX.sty
> ('x'-->'X')!
>ls c:/data/develop/tex/texmf/tex/generic/dratex/AlProTeX.sty
/dev/fs/C/data/develop/tex/texmf/tex/generic/dratex/AlProTex.sty
>kpsewhich AlProTeX.sty
c:/data/develop/tex/texmf/tex/generic/dratex/AlProTeX.sty
>luatools AlProTeX.sty
c:/data/develop/tex/texmf/tex/generic/dratex/AlProTex.sty
so, the file actually is named with an 'x' ; luatools (i.e. the file
handler written in lua) can handle mixed cases in a way that it will
always resolve to the syetem filename, here the one with th elower case
x; so i guess that kpse is reporting wrong
is there an alias file involved (i ignore that one, actually alias files
are not supposed to exist any longer)
> For testing, you can just set some simplified TEXMF, e.g.,:
>
> export TEXMF={$HOME/texmf,/usr/local/texmf,/usr/share/texmf-texlive,/usr/share/texmf}
>
> or you can edit /etc/texmf/texmf.d/05TeXMF.cnf to simplify things like:
>
> TEXMFDIST = /usr/share/texmf-{texlive,tetex}
>
> In my case, I no longer have texmf-textex, so this became just
>
> TEXMFDIST = /usr/share/texmf-texlive
>
> Then run: "update-texmf" and "luatools --generate"
>
> You can check the TEXMF variable with:
>
> $ luatools --expand-var TEXMF
>
> More tests to make sure the configuration is working:
>
> $ luatools msam7.afm
> /usr/share/texmf-texlive/fonts/afm/bluesky/ams/msam7.afm
>
> Then build the format:
>
> $ luatools --ini --verbose --compile cont-en
>
> and compile something:
>
> $ texexec --luatex foo
> TeXExec | processing document 'foo'
> TeXExec | no ctx file found
> TeXExec | tex processing method: context
> TeXExec | TeX run 1
> TeXExec | writing option file foo.top
> TeXExec | using randomseed 967
> TeXExec | tex engine: luatex
> TeXExec | tex format: cont-en
>
> This is luaTeX, Version 3.141592-beta-0.11.2-2007092410 (Web2C 7.5.6)
> (./foo.tex
>
> ConTeXt ver: 2007.09.28 16:52 MKIV fmt: 2007.10.12 int: english/english
> [...]
btw, i have to find a way to report that a cache path is not present of
writable
Hans
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2007-10-12 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 15:10 George N. White III
2007-10-12 16:11 ` Hans Hagen [this message]
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=470F9CAE.20905@wxs.nl \
--to=pragma@wxs.nl \
--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).