[tex-live] Bizarre perforce situation

Gerben Wierda Gerben.Wierda at rna.nl
Sat Feb 7 08:59:47 CET 2004

The bizarre thing is that this was all ok before and when I extract the 
source tree (*not* source.development) from TL4 (Sep 2003) gives me a 
texmf.in and a texconfig which calls kpsewhich to find pdftex.cfg and 

Now, given that I put that release out in September of last year I am 
pretty sure it worked. It looks like p4 is serving me completely wrong 


On Feb 7, 2004, at 8:27 AM, Thomas Esser wrote:

>> Now the bizarre thing. When I currently do the p4 sync I get
>> 3.141592-1.11b. And this 1.11b version is incompatible with the texmf
>> tree that make install from TL produces. That texmf.cnf has
> pdftex 1.11b does not yet use the new search path that is set up by
> $PDFTEXCONFIG. The config file is still used along $TEXINPUTS.
>> $TEXMF/pdftex/config/pdftex.cfg
> So, you have to make sure that your TEXINPUTS.pdf<something>
> search paths are set up to search texmf/pdftex//
>> Now the weird thing is that this should work. After all, the texmf.cnf
>> and pdftex are from the same release. But it doesn't.
> Sometimes, things are not "in sync". E.g. currently, dvips is broken in
> TeX Live's source.development. I could fix it, but I am not the 
> maintainer
> for this part, so I sit down and wait.
> After I have done changes to kpathsea, it took just a few days until
> Martin has updated pdftex in source.development, and now we have them.
> I have no idea how the schedule for updating the Build/source tree is.
> I leave this up to Sebastian.
> Thomas
> _______________________________________________
> TeX Live mailing list
> http://tug.org/mailman/listinfo/tex-live

More information about the tex-live mailing list