Re: git vs git

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Jan 30, 2006, 20:16 UTC
Message-ID: <46a038f90601301216n793f0eb5k34a2b5a7c4e7491e@mail.gmail.com>
In-Reply-To: <d93f04c70601300714i4b7b3b58qa5aa151e3e42a413@mail.gmail.com>

On 1/31/06, Hendrik Visage <hvjunk@gmail.com> wrote:

> git isn't
> working because the wrong git is in the right place :(

Well, I just hit this yesterday on a colleage's machine who was trying to get going with git.His first try was to `apt-get install git` and as that didn't lead anywhere he fetched the git (scm) sources and built them.

Apparently GNU GIT's git binary was earlier in the path than GIT SCM's and so stuff broke very creatively. As soon as I did `git --version` I understood what was happening and a swift `apt-get remove git` fixed it. But it can sure mess the day for any user trying to install git naively.

Not sure how to deal with this. Packages already record (or can record) it as a conflict, but source built stuff is different. Perhaps during `make install` we should try and exec git --version towards the end and print a big fat warning?

cheers,