Hi,

...

I generate format with bin/texexec --make --alone en nl metafun but the format files go somewhere else! Even with --alone. from the logfile: used formatpath : /var/tmp/tetex3/texmf-sysvar/web2c/ I need to switch between different context versions and I'd like to have the format file in web2c/... subdir.

is that the latest texexec, posted last night?

Yes

isn't there an engine path?

No, what is an engine path? A subdir of web2c like web2c/pdfetex/ ? I am used to have --alone leave my format files in place. This doesn't work here anymore. BTW: I can't stop texexec/pdftex with CTRL-C. Would it be rude to ask to remove $SIG{INT} = "IGNORE"; from texexec? Patrick -- ConTeXt wiki and more: http://contextgarden.net

...

I am used to have --alone leave my format files in place. This doesn't work here anymore.

actually the leaving it in place was a bug there; now we always run alone (i removed fmtutil support); should i provide a switch --local?

that would be nice. I just tried texmfstart mktexlsr: Done. TeXExec | using tex engine pdfetex TeXExec | using tex format path /var/tmp/tetex3/texmf-sysvar/web2c/pdfetex /opt/context/current/texmf/scripts/context/ruby/base/tex.rb:239:in `initialize': Permission denied - cont-fmt.tex (Errno::EACCES) from /opt/context/current/texmf/scripts/context/ruby/base/tex.rb:239:in `open' from /opt/context/current/texmf/scripts/context/ruby/base/tex.rb:239:in `openedfile' from /opt/context/current/texmf/scripts/context/ruby/base/tex.rb:548:in `makeuserfile' from /opt/context/current/texmf/scripts/context/ruby/base/tex.rb:406:in `makeformats' from /opt/context/current/texmf/scripts/context/ruby/newtexexec.rb:47:in `make' from /opt/context/current/texmf/scripts/context/ruby/newtexexec.rb:592:in `send' from /opt/context/current/texmf/scripts/context/ruby/newtexexec.rb:592

...

BTW: I can't stop texexec/pdftex with CTRL-C. Would it be rude to ask to remove $SIG{INT} = "IGNORE"; from texexec?

hm, how about newtexexec.rb ? texexec.pl will go away anyway

that would be fine with me. I lived with it for a couple of years, so no need to hurry :-) I am slightly annoyed by the changes in the tex-engines for some time now. All those changes in the web2c layer where it looks as if backward compatiblity is available but in reality it is not. Currently I am losing interest in staying up to date since I am convinced that everything will change again in half a year or one year from now, with even more magic in all those 1000s of config parameters/files/scripts. Patrick -- ConTeXt wiki and more: http://contextgarden.net

Hi, [...]

...

TeXExec | using tex format path /var/tmp/tetex3/texmf-sysvar/web2c/pdfetex /opt/context/current/texmf/scripts/context/ruby/base/tex.rb:239:in `initialize': Permission denied - cont-fmt.tex (Errno::EACCES)

hey, what does this mean; that the var dir is non writable?

No, it is writable: /var/tmp/tetex3/texmf-sysvar/web2c$ mkdir pdftex /var/tmp/tetex3/texmf-sysvar/web2c$ ls -d pdftex pdftex

in this tex.rb file, can you replace

def openedfile(name) begin f = File.open(name,'w') rescue report("file '#{File.expand_path(name)}' cannot be opened for writing") return nil else cleanuplater(name) if f return f end end

and see what happens? btw, the cont-fmt file holds format generatation parameters (also in texexec.pl)

error again TeXExec | using tex engine pdfetex TeXExec | using tex format path /var/tmp/tetex3/texmf-sysvar/web2c/pdfetex TeXExec | file '/var/tmp/tetex3/texmf-sysvar/web2c/pdfetex/cont-fmt.tex' cannot be opened for writing TeXExec | file '/var/tmp/tetex3/texmf-sysvar/web2c/pdfetex/mult-def.tex' cannot be opened for writing TeXExec | generating tex format cont-en TeXExec | pdfetex --progname=context --ini --translate-file=natural.tcx *cont-en This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (INITEX) (/opt/context/current/texmf/web2c/natural.tcx) entering extended mode ! I can't write on file `cont-en.log'. But to repeat myself: I do not want texexec or any other program to write the format file there. I can find the format file with kpsewhich in /opt/context/... and texexec should use this information. No need for multiple format files in different places. [...]

unfortunately the last few years downward compatibility is dropped at the binarty / tds level, which is in my opinion a bad thing (part can be catched by a different texsmf.cnf file, e.g. context.cnf)

Well, texexec also just broke compatibility by introducing a different behaviour to --alone and fiddling with the TeX search path in the background. IMO texexec should not try to do "everything". Generating the format is fine, but don't try to guess where to place the format for *every* distributon.

the fact that you use tetex does not help much since it's meant as a install from scratch and forget about your own stuff' kind of environment.

So what distribution would serve me better? Patrick -- ConTeXt wiki and more: http://contextgarden.net

[...]

watch my mailbox about users who have no clue where to put fotmats -)

OK, +1 for you :-)

...

So what distribution would serve me better?

just take the minimal

one day I'll give it a try. Patrick -- ConTeXt wiki and more: http://contextgarden.net

Taco Hoekwater wrote:

Hi,

It works for me (texexec is 5.4.1), but only after I renamed context.cnf to texmf.cnf. The last path message from my (identical) commandline is indeed without the engine path:

used formatpath : /home/taco/texmf/web2c/

but that is simply because the last format is metafun, and metapost does not use an engine path. I have cont-en.fmt and cont-nl.fmt in subdir /home/taco/texmf/web2c/pdfetex, as

ah, so it finally works!

expected. Perhaps your problem is related to the change in context.cnf (the latest uses a different variable name for engine path).

indeed, $engine is lowercase (not uppercase as the other vars); i already asked olaf to set both lower an duppercase vars 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 -----------------------------------------------------------------

Patrick Gundlach wrote:

Hi,

[...]

...

expected. Perhaps your problem is related to the change in context.cnf (the latest uses a different variable name for engine path).

I don't use context.cnf, do I? (Actually, it is the first time I've heard of this file).

It is a texmf.cnf-in-disguise, that contains the right settings that are needed for e.g. $engine support. It was first included in the 20050525, so it is not a surprise you have not seen it yet. Taco

Patrick Gundlach wrote:

Hi,

...

It works for me (texexec is 5.4.1), but only after I renamed context.cnf to texmf.cnf. The last path message from my

I don't want to use a different texmf.cnf for security reasons. So this is currently a showstopper. I really like to get the old behaviour back!

can you be more specific about this 'old behavour' you want back? if i know what, i can provide a switch 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 -----------------------------------------------------------------

Patrick Gundlach wrote:

...

can you be more specific about this 'old behavour' you want back?

--alone keeping the format files in situ. But the --local switch that you've mentinoned would be fine.

ok, --local it will be then since --alone (on my machine) always moved toe files to the tree; also, the --alone switch is gone, it was needed to bypass fmtutil which is not used anymore. 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 -----------------------------------------------------------------