Re: [NTG-context] Another texmfstart question
Jean Magnan de Bornier wrote: Hi all, I just made on my linux-gentoo box a fresh install using (exactly) this howto: http://wiki.contextgarden.net/TeTeX_3.0_installation But using texmfstart texexec toto gives texmfstart not found; I tried with the full path of texmfstart.rb and get permission denied; so I go into the directory /usr/local/teTeX/share/texmf-local/scripts/context/ruby and see that many scripts are not executable for others (regular users); so I say chmod +x * in that directory and then texmfstart texexec toto still doesn't work but it actually works with the full path; however my path is correctly set for context afaik. I tried to set $RUBYLIB to this directory but it doesn't change anything. only texmfstart needs to be executable 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Another texmfstart question
On 5/29/06, Jean Magnan de Bornier [EMAIL PROTECTED] wrote: Hi all, I just made on my linux-gentoo box a fresh install using (exactly) this howto: http://wiki.contextgarden.net/TeTeX_3.0_installation But using texmfstart texexec toto gives texmfstart not found; I tried with the full path of texmfstart.rb and get permission denied; so I go into the directory /usr/local/teTeX/share/texmf-local/scripts/context/ruby and see that many scripts are not executable for others (regular users); so I say chmod +x * in that directory and then texmfstart texexec toto still doesn't work but it actually works with the full path; however my path is correctly set for context afaik. On my systems, teTeX-3 does not include a texmfstart executable. One approach is to copy the texmfstart.rb script to texmfstart in a directory on your PATH. Earlier, I posted a script I have been testing to the list. The script uses kpsewhich to find the .rb or .pl script corresponding to the name used to invoke the script, and then runs perl or ruby with the full path to the script. This saves having to copy the scripts everytime you update context. I tried to set $RUBYLIB to this directory but it doesn't change anything. RUBYLIB is set in the setuptex script from the minimal linux. For my simple tasks it doesn't appear to be needed, but setting it shouldn't hurt. -- George N. White III [EMAIL PROTECTED] Head of St. Margarets Bay, Nova Scotia ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Another texmfstart question
Le 29 mai à 13:47:04 [EMAIL PROTECTED] écrit notamment: | On my systems, teTeX-3 does not include a texmfstart executable. One approach | is to copy the texmfstart.rb script to texmfstart in a directory on your PATH. | Earlier, I posted a script I have been testing to the list. The | script uses kpsewhich | to find the .rb or .pl script corresponding to the name used to invoke | the script, and then runs perl or ruby with the full path to the | script. This saves having to copy the scripts everytime you update | context. Thank you and Hans, I'll look for your script asa I go back to my other machine; I must confess (no criticism) that I'm a bit surprised things like that are left to every user to deal with, as the rest of context is so elaborated. cheers, -- Jean ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Another texmfstart question
Jean Magnan de Bornier wrote: Le 29 mai � 13:47:04 [EMAIL PROTECTED] �crit notamment: | On my systems, teTeX-3 does not include a texmfstart executable. One approach | is to copy the texmfstart.rb script to texmfstart in a directory on your PATH. | Earlier, I posted a script I have been testing to the list. The | script uses kpsewhich | to find the .rb or .pl script corresponding to the name used to invoke | the script, and then runs perl or ruby with the full path to the | script. This saves having to copy the scripts everytime you update | context. Thank you and Hans, I'll look for your script asa I go back to my other machine; I must confess (no criticism) that I'm a bit surprised things like that are left to every user to deal with, as the rest of context is so elaborated. cheers, well, the problem is that each distribution does it different; the whole idea behind texmfstart is that one you have that one script running, all others should work as well since one cna say: texmfstart texexec somefile to process a file,and similarily: texmfstart ctxtools texmfstart rlxtools texmfstart pdftools texmfstart tmftools texmfstart textools texmfstart pstopdf and what else is distributed with context 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context