[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 85Misc



On Wed, Sep 04, 2002 at 11:32:22PM +0900, Atsuhito Kohda wrote:
> I didn't mean to change texk/kpathsea/texmf.in directly
> but I did mean to change texmf.d/85Misc which is completely
> irrelevant to compilation, that is, at compile time the
> generated texmf.cnf in texk/kpathsea will be used as before.
> 
> If TEXMFCNF isn't read at run-time as you explained then 
> there might be not so much difference between the current 85Misc
> and the modified one, but at least from esthetic point of view, 
> no duplication might be better.
> 
> Am I missing something important?

The only purpose of the TEXMFCNF line in the texmf.cnf file is so that
people can see what was used during compilation of the TeX binary, and
therefore what is actually being used.  Changing this is therefore not
helpful.  If we really are getting a path with unnecessarily repeated
components, the place to change is is texmf.in, and then modify
texmf.d/85Misc to reflect these changes.

   Julian

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London
              website: http://www.maths.qmul.ac.uk/~jdg/
   Debian GNU/Linux Developer, see: http://people.debian.org/~jdg/
     Visit http://www.thehungersite.com/ to help feed the hungry



Reply to: