Re: Strangely hosed git install

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: May 28, 2009, 10:11 UTC
Message-ID: <46a038f90905280311p406a528atb8d21a30fe53b0e3@mail.gmail.com>
In-Reply-To: <4A1E5DBC.2090908@drmicha.warpmail.net>

On Thu, May 28, 2009 at 11:47 AM, Michael J Gruber <git@drmicha.warpmail.net> wrote:

> This is insane. Don't they even distinguish between an interactive shell
> and a non-interactive one?

Yes they do. I mentioned it but I didn't think it was the reason behind the problem.

> Well, I would say go "find / git-diff-index", or simply nuke anything
> git you find and do a clean install... "find"ing the left over bits
> would help making sure that git's own search path is OK.

well, that's not what happens when people bisect back and forth. It used to be reasonably safe, it got unsafe when we moved lots of things to libexec (and therefore the make install target got a nice warning message about it). Now there might something acting up again.

Alas, I didn't keep a backup of my libexec :-/

-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff