> Of course it's the purpose of /usr/local/(share/)texmf to be able to > override and shadow files in /usr/share/texmf, so it is of course in > order that it picks up these files. It did the same in woody, but it > just happened that the woody versions and the versions in /usr/local > matched, whereas the sarge versions have changed. And pool files are > closely associated at compile time to the binaries; that's why they are > in tetex-bin, not in tetex-base.
I'm starting to understand. Thanks for this clarification. > > On our remaining woody boxes I have tetex-extra > > 1.0.2+20011202 installed. Is this behaviour I am seeing the result of a > > fix for wrong behaviour in that older version? > > No, neither a wrong behaviour nor a fix. You just have to remove all > *.pool files (and probably also *.tcx) from the local tree. ok. I notice that those files appeared just within the last two weeks, so I think the cause of my problem is quite clear (it's my end). Thanks for your answers and patience. Do you need additional info or tests to be able to close this bug, btw? Vince -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
