Latest version of teTeX

Kay Lehmann kay_lehmann at
Fri May 14 14:42:23 PDT 2004

Stephen Montgomery-Smith wrote:
> Hiroki Sato wrote:
>> should be created by ${PKGINSTALL} script if ${WITH_DVIPSK}
>>  is defined.  Wasn't it created in your environment?
> No it wasn't.  And looking inside the teTeX Makefile, it is not clear to 
> me how it should have been created.
> Also, if I create the teTeX port without WITH_XDVIK being defined, then 
> the texconfig command simply does not work, it has an error message to 
> the effect that some kind of xdvi config file could not be read.
> Also, I have a problem with WITH_DVIPSK and WITH_XDVIK being undefined 
> by default.  This means that when the next set of packages is made, the 
> user who installs teTeX from the packages will not have xdvi or dvips 
> installed.  This will come as a surprize.  So then he will install the 
> xdvi package, which it seems is incompatible with teTeX.  So then he 
> realises that he should install the xdvik package - well this would take 
> some guesswork - I mean, why the "k"? So then he looks around for the 
> dvipsk package in vain.  And having xdvik installed, the texconfig 
> command is still not working.
> It seems to me that the teTeX program is designed so that dvips and xdvi 
> are built with it, and any attempts to modify the build procedure should 
> be done with extreme care.
> Stephen


just want to tell that I am not a real fan of the last changes to teTeX, 
too. First of all I was somehow confused that after updating tetex I did 
not have any dvips or xdvi packages, since Ithought dvipsk and xdvik are 
the japanese versions of these progs and the default options wouldn't 
affect me as non japanese user. Then I decided to install the sepeate 
ports and ran into some selfmade problems. Next step for me was to 
deinstall all three ports and reinstall tetex with WITH_DVIPSK and 
WITH_XDVIK enabled. Next I recognized some odd paperprobs and found 
dvips was using letter as default paper. So I tried to use texconfig 
which doesn't work at all. After looking at the previous posts in this 
thread I took a look at (which semm to be created in my case) 
and saw that everything was commented out. After editing this file by 
hand everything works as it should again now.
Okay this was my story. So in opinion it would be much better to install 
xdvi and dvips by default since they are definitly part of tetex and 
should stay a part of tetex. And maybe the problems 
will be gone again. I think it would be much better not using these 
options if everything works as expected after installation of tetex and 
note users of the seperate ports that they need to deinstall these if 
they want to use tetex. That's just my opinion, but I thought it may 
help finding a solution.


More information about the freebsd-ports mailing list