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

Re: 85Misc



From: Julian Gilbey <J.D.Gilbey@qmul.ac.uk>
Subject: Re: 85Misc
Date: Wed, 4 Sep 2002 15:59:51 +0100

> 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.

I see.  So duplication in our system tells us that
we used $TEXMF/web2c=@web2c@ at compile-time.

And there is possibility that $TEXMF/web2c is not @web2c@
in some cases so it is very bad to change texmf.in, it will
lost generality.

Okay, Hans, this duplication in 85Misc is very informational
and should be duplicated.

I will revert the change soon and thanks Julian.

Best regards,		      2002/9/5

-- 
 Debian Developer & Debian JP Developer - much more I18N of Debian
 Atsuhito Kohda <kohda@debian.org>
 Department of Math., Univ. of Tokushima



Reply to: