Re: intended use of "git --exec-path"?

From: David Symonds <dsymonds@gmail.com>
Date: Oct 24, 2007, 05:54 UTC
Message-ID: <ee77f5c20710232254j32afa044t841b4a4f6fcdfd7d@mail.gmail.com>
In-Reply-To: <20071024054749.GT16291@srparish.net>

On 10/24/07, Scott Parish <sRp@srparish.net> wrote:

Show 18 quoted lines

> On Wed, Oct 24, 2007 at 12:38:19AM -0400, Shawn O. Pearce wrote:
>
> > Scott Parish <sRp@srparish.net> wrote:
> > > "git --exec-path" presently prints out the highest priority path
> > > to find executable in. That's a what; i'm curious why and when it
> > > should be used. Basically i'm wondering if its still useful, and
> > > what, if anything, it should be printing.
> >
> > git-gui uses it.  git-gui runs git-* by prefixing it with the
> > exec path.  It also scans the first line of the file if we are on
> > Windows and the "executable" doesn't end in ".exe" so it can figure
> > out what process to run it through.
> >
> > So it really can't go away.
>
> So it sounds like it might be more helpful for git to return its
> PATH, so other programs can set their PATH or search for executables
> accordingly.

You don't necessarily want to be monkeying around with $PATH if you're trying to use a particular git installation (say, a build of next) instead of your "proper" install, which is in your $PATH; if you call /some/random/path/git-whatever, it should use the git tools in /some/random/path/, not in $PATH.

Dave.