automake
[Top][All Lists]
Advanced

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

Re: [Fwd: --add-missing]


From: Tom Tromey
Subject: Re: [Fwd: --add-missing]
Date: 25 Nov 2000 18:52:30 -0700

>>>>> "Derek" == Derek R Price <address@hidden> writes:

Derek> Yep.  Looks like that could be used by configure to set, say,
Derek> TEX_TEXINPUTS & PDFTEX_TEXINPUTS and prepend include dirs
Derek> differently for different targets, but I suspect that if your
Derek> TeX distribution includes kpsewhich then your TeX applications
Derek> can already find the appropriate texinfo.tex.

Me too.  But the point is that GNU packages are supposed to ship with
texinfo.tex.

I'm reluctant to rely on kpsewhich.  What if we changed makeinfo to
have an option to print the path to texinfo.tex?  Then automake could
run this program instead of installing its own private copy of
texinfo.tex.

This would guarantee that the maintainer gets the texinfo.tex that
matches his makeinfo.

Tom



reply via email to

[Prev in Thread] Current Thread [Next in Thread]