texi2dvi finding other programs

[Karl Berry]

Hi again, 

    texi2dvi will call makeinfo and texindex from the very same directory

I don't think we shouldn't absolutely force makeinfo et al. to be be in
the same dir as texi2dvi; people might invoke texi2dvi in the sources (I
do this myself) and there's no reason to make that fail.

We could add $bindir (with absolute_filenames applied) first to PATH --
I made the "patch below" show my version of doing that.  But I am
somewhat loath to tinker with the user's PATH, just on general
principles.

What do others think?

Other ideas:
Can you just put /usr/local/bin in your path before /usr/bin?  Or will
there be an issue for users after you have the port done?

    texi2dvi (new) calling texindex (old) causes texindex to dump core.

I can't think of any reason for this -- old and new texi2dvi should be
basically the same invocation, and it should be pretty much the same
index files.  Unless the old texindex is simply completely broken on
your system?

Thanks,
karl


Date: Sun, 13 Mar 2005 14:51:24 +0100
From: Matthias Kilian <address@hidden>
To: Karl Berry <address@hidden>
Subject: Minor texi2dvi patch

Hi,

On Sat, Mar 12, 2005 at 08:38:06AM -0500, Karl Berry wrote:
> Thanks very much.

Not for this ;-)

Could you consider also applying the patch below? It ensures that
texi2dvi will call makeinfo and texindex from the very same directory
itself is installed.

Reason:

Under normal circumstances, that's no problem, but I'm trying to
get this up and running on OpenBSD (for LilyPond), and OpenBSD
contains it's own (little bit outdated) version of the texinfo suite
in /usr/bin. Since I'm doing a *port* for 4.8, it get's installed
in /usr/local/bin. This causes intermixing old and new texinfo stuff
depending on the PATH. At least on macppc, texi2dvi (new) calling
texindex (old) causes texindex to dump core.

Ciao,
        Kili

--- texi2dvi    2005-03-13 06:46:19.000000000 -0800
+++ /tmp/t2d    2005-03-13 06:39:18.000000000 -0800
@@ -120,2 +120,7 @@
 
+# Prefer programs in the same directory as we are.
+bindir=`dirname $0`
+absbindir=`absolute_filenames "$bindir"`
+PATH=$absbindir:$PATH
+
 # In case someone crazy insists on using grep -E.