Texlive 2008 and luatools
Hi, Texlive 2008 works perfectly with Context, but I have one question regarding luatools. I am posting this here rather than on TL mailing list, since I do not want to cause more confusion on TL regarding ConTeXt. In the bin directory in minimals, luatools is a copy of luatools.lua. This means that one does not need ruby in order to run luatools. It also means that whenver you upgrade your system, you need to run luatools --selfupdate. In TL2008, luatools is a wrapper script. #!/bin/sh texmfstart luatools.lua "$@" This means that you need to have ruby in order to run luatools. The advantage is that you do not need to run luatools --selfupdate. In terms of speed, there is a slight disadvantage, you first start ruby, and then start texlua. Using a wrapper script was suggested by Taco on the mailing list. If TL is to use a wrapper scipt, why not simply #!/bin/sh mtxrun --script luatools "$@" this will mean that you do not start ruby before moving to lua. In both cases, one has to do mtxrun --selfupdate after a update that changes mtxrun. This is not really important, since luatools will be run rarely. Do you think that the current texmfstart wrapper should be changed to a mtxrun wrapper? Aditya
Aditya Mahajan wrote:
Hi,
Texlive 2008 works perfectly with Context, but I have one question regarding luatools. I am posting this here rather than on TL mailing list, since I do not want to cause more confusion on TL regarding ConTeXt.
In the bin directory in minimals, luatools is a copy of luatools.lua. This means that one does not need ruby in order to run luatools. It also means that whenver you upgrade your system, you need to run luatools --selfupdate.
In TL2008, luatools is a wrapper script.
#!/bin/sh texmfstart luatools.lua "$@"
This means that you need to have ruby in order to run luatools. The advantage is that you do not need to run luatools --selfupdate. In terms of speed, there is a slight disadvantage, you first start ruby, and then start texlua. Using a wrapper script was suggested by Taco on the mailing list.
having a 'copy' or 'symlink' is indeed the best for luatools and mtxrun, and using texmfstart for it is at some point going to fail
If TL is to use a wrapper scipt, why not simply
#!/bin/sh mtxrun --script luatools "$@"
this will mean that you do not start ruby before moving to lua. In both cases, one has to do mtxrun --selfupdate after a update that changes mtxrun.
i prefer both mtxrun and luatools to be handled as programs and not being stubbed (in a luatex specific installation there won;t even be a texmfstart anyway and i'm thinking of replacing texmfstart by mtxrun at somepoint)
This is not really important, since luatools will be run rarely. Do you think that the current texmfstart wrapper should be changed to a mtxrun wrapper?
at some point i might replace luatools by mtx-tools so that we only have mtxrun; i could not combine both because they have a different set of flags but in that case luatools would be a simple stub like 'context' is currently 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 -----------------------------------------------------------------
Hi, Hans Hagen wrote:
Aditya Mahajan wrote:
In TL2008, luatools is a wrapper script.
#!/bin/sh texmfstart luatools.lua "$@"
That is by my suggestion. After all the other manual labor texlive users will have go through just to get mkiv running, I did not want to scare them even more by forcing them to use --selfupdate. Especially since --selfupdate fails in a non-zero amount of cases, and if that would happen to a user not on ntg-context they would be utterly lost.
having a 'copy' or 'symlink' is indeed the best for luatools and mtxrun, and using texmfstart for it is at some point going to fail
This would work fine if --selfupdate was totally reliable, but it isn't. Whenever a new library appears in the distro there is a chance that selfupdate will fail. I've had that happen a number of times. It is ok for me (I know what to do), but not acceptable casual users. Best wishes, Taco
participants (3)
-
Aditya Mahajan
-
Hans Hagen
-
Taco Hoekwater