Hans Hagen wrote:
Sanjoy Mahajan wrote:
Actually, on my system (Ubuntu, a Debian derivative), changing the texmf.cnf file directly is not a good idea. Instead one should change the same line in /etc/texmf/texmf.d/95NonPath.cnf and then run 'update-texmf' as root to generate the texmf.cnf file.
incredible (probably a copy of texmf.cnf in your local tree also works ok; in that case: clean up the file a bit and things run faster too)
Yeah, it's a pain but it does have one justificaiton. This texmf.cnf system is easy for computers to update, although not for people. The idea is that new tex-related packages add options by placing the options in a file in /etc/texmf/texmf.d/ and then running update-texmf to combine the configlets into the One File to rule them all. The diversity of configuration systems and options across different tex installations is a big pain, makes it hard to create cross-platform software. -Sanjoy `Never underestimate the evil of which men of power are capable.' --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.