Re: [dev-context] context program, mtxrun question?
Hi again, (replying to myself) Taco Hoekwater wrote: > Oliver, I have emailed you a patched version of luatools.lua. Can > you try to make sure that it works for you as well? (It should, but ...) Hans is just finished uploading a new beta that has two fixes in this area: * there was a bug in the TEXMFCACHE defaulting, making it ask strange questions if TEXMFCACHE was not set in texmfcnf.lua. * it comes with a variation of the symlink-discovering code I posted earlier. There is an extra report line if a symlink is followed while discovering the full executable path. e.g.: LuaTools | following symlink /home/taco/mybin to /usr/local/bin The chosen method has a few small flaws in bordercases that will be corrected eventually (in a new luatex release) but it seems to work well enough for now Best wishes, Taco ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] context program, mtxrun question?
Taco Hoekwater wrote: > > The chosen method has a few small flaws in bordercases that will > be corrected eventually (in a new luatex release) but it seems > to work well enough for now Before Oliver tells me I am being vague again: ;-) What I mean is this: in the full path "/usr/texbin/luatex", "texbin" can be a symlink to a different directory and that will be followed, but if "luatex" itself is a symlink to a file in a different directory, that will not be noticed. Solving that in pure lua is pretty hard, so I will add a predefined "full executable path" variable in the next luatex beta. Best wishes, Taco ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] context program, mtxrun question?
Hans Hagen wrote:
> Oliver Buerschaper wrote:
>
>> Obviously, the problem is the symbolic link because LuaTeX tries and
>> finds argv[0] in $PATH but doesn't resolve /usr/texbin to its actual
>> location on disk. It's clear that in this situation there can't be
>> any difference between the distribution-independent syntax of
>> calling luatex and the direct invocation.
>>
>> Do you think LuaTeX's path discovery mechanism could be adapted to
>> handle symbolic links?
>
> there is lfs.symlinkattributes but i'm somewhat reluctant to usinmg
> platform specific things; if i have time i'll see if this function
> returns something useful
No need, here is function that works and is portable to all platforms:
function input.getownpath()
local olddir = lfs.currentdir()
if not input.ownpath then
for p in
string.gmatch(os.getenv("PATH"),"[^"..io.pathseparator.."]+") do
lfs.chdir(p)
p = lfs.currentdir()
local b = file.join(p,input.ownbin)
if lfs.isfile(b..".exe") or lfs.isfile(b) then
input.ownpath = p
break
end
end
if not input.ownpath then input.ownpath = '.' end
end
lfs.chdir(olddir)
return input.ownpath
end
Oliver, I have emailed you a patched version of luatools.lua. Can
you try to make sure that it works for you as well? (It should, but ...)
Best wishes,
Taco
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] context program, mtxrun question?
Oliver Buerschaper wrote: > Obviously, the problem is the symbolic link because LuaTeX tries and > finds argv[0] in $PATH but doesn't resolve /usr/texbin to its actual > location on disk. It's clear that in this situation there can't be any > difference between the distribution-independent syntax of calling > luatex and the direct invocation. > > Do you think LuaTeX's path discovery mechanism could be adapted to > handle symbolic links? there is lfs.symlinkattributes but i'm somewhat reluctant to usinmg platform specific things; if i have time i'll see if this function returns something useful 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 - ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] context program, mtxrun question?
Hi Taco,
> This new release is available now.
I've just had the chance to test this new release and got mixed
results ... the 2008.05.21 minimal distribution (LuaTeX only) now sits
in
/usr/local/context/2008-05-21
and there's a symbolic link
/usr/texbin -> /usr/local/context/2008-05-21/texmf-osx-intel/bin
to the binaries. This link is given by the distribution switching
mechanism on the Mac (see my earlier post in this thread) and is
appended to $PATH, too. Furthermore, *no* TEXMFCNF environment
variable is set.
Now there's a problem of finding the texmf.cnf file:
---
$>/usr/texbin/luatools --generate --verbose
LuaTools | version 1.2.0 - 2006+ - PRAGMA ADE / CONTEXT
LuaTools | variable SELFAUTOLOC set to /usr/texbin
LuaTools | variable SELFAUTODIR set to /usr/texbin/..
LuaTools | variable SELFAUTOPARENT set to /usr/texbin/../..
LuaTools | variable TEXMFCNF set to {$SELFAUTODIR,$SELFAUTOPARENT}{,{/
share,}/texmf{-local,.local,}/web2c}
LuaTools | no cnf files found (TEXMFCNF may not be set/known)
LuaTools |
LuaTools | runtime: 0.004 seconds
---
The problem persists when I call the binary directly:
---
$> /usr/local/context/2008-05-21/texmf-osx-intel/bin/luatools --
generate --verbose
LuaTools | version 1.2.0 - 2006+ - PRAGMA ADE / CONTEXT
LuaTools | variable SELFAUTOLOC set to /usr/texbin
LuaTools | variable SELFAUTODIR set to /usr/texbin/..
LuaTools | variable SELFAUTOPARENT set to /usr/texbin/../..
LuaTools | variable TEXMFCNF set to {$SELFAUTODIR,$SELFAUTOPARENT}{,{/
share,}/texmf{-local,.local,}/web2c}
LuaTools | no cnf files found (TEXMFCNF may not be set/known)
LuaTools |
LuaTools | runtime: 0.007 seconds
---
Obviously, the problem is the symbolic link because LuaTeX tries and
finds argv[0] in $PATH but doesn't resolve /usr/texbin to its actual
location on disk. It's clear that in this situation there can't be any
difference between the distribution-independent syntax of calling
luatex and the direct invocation.
Do you think LuaTeX's path discovery mechanism could be adapted to
handle symbolic links?
All the best,
Oliver
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] modules at supelec
> Fabrice is expecting suggestions about some new hierarchy on supelec, > to be able to find TeX-related projects more easily. I need to know gforge a bit more than now. Maybe a (sub)Topic 'typesetting' in Trove http://foundry.supelec.fr/softwaremap/trove_list.php -- luigi ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] modules at supelec
On Sat, May 24, 2008 at 11:10 AM, luigi scarso <[EMAIL PROTECTED]> wrote: > Hi all > I start modules project at > http://foundry.supelec.fr/projects/modules > > Suggestions are welcome , of course. Fabrice is expecting suggestions about some new hierarchy on supelec, to be able to find TeX-related projects more easily. Mojca ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
[dev-context] modules at supelec
Hi all I start modules project at http://foundry.supelec.fr/projects/modules Suggestions are welcome , of course. Thank you all -- luigi ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] context program, mtxrun question?
Martin Schröder wrote: > 2008/5/23 Hans Hagen <[EMAIL PROTECTED]>: >> sure, but it depends on tmp being cleaned up too; afaik /tmp and c:/temp >> are only cleaned up periodically e.g. when one runs out of space so it's >> a kind of indication of 'may be cleaned up' > > Many Unixes clear /tmp at bootup. Even SUSE can do this. :-) > > http://en.wikipedia.org/wiki/Temporary_directory > "In Unix and Linux, the global temporary directories are /tmp and > /var/tmp. Typically, /var/tmp is for more permanent files, and /tmp is > for more temporary files. See Filesystem Hierarchy Standard. In > addition, a user can set his TMPDIR environment variable to point to a > preferred directory (where the creation and modification of files is > allowed)." so then checking for TMPDIR should precece TMP - 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 - ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
