Am Montag, den 07.April 2003 um 20:08 schrieb Hans Hagen:
there is much more than just running mpost as you have probably seen.
Can someone summarize the problem?
Hans
The problem was the following: Using the "original" texexec.pl that was installed on my Debian unstable system, using MetaPost in a ConTeXt-file was not handled correctly: \starttext ... \start..MP label("test", (0,0)) \stop..MP \stoptext would work correctly; the MP instructions would be written into mpgraph.mp and converted to PS on-the-fly (if using automprun). If you would use MPcode that uses btex: ... \startMP label(btex test etex, (0,0)) \stopMP ... it would not work; you'll have to run "mpost mpgraph" after running texexec to create the PS file. Trying to solve the problem, I've found that after texexec calles e-TeX to typeset the 'btex ... etex' part, the file mpgraph.mp would be overwritten. Texexec, it is true, keeps a backup of the original mpgraph but seems to restore it _after_ calling mpost on it (which results in MetaPost compiling a file that contains only an 'end.') I have posted my patch to this problem, and asked if someone knows whether the late restoral was intended or a bug. Hope this somewhat clears the matter, Dennis