Chris OrtmanUp until today I've always run git off whatever debs come with ubuntu. But if I'm going to try to do some work I figured I should be compiling from source.
To compile I did git co -b current v1.5.3.8 make make install
then to check which git /home/chrisortman/bin/git as expected
however git --version still reports 1.5.2.5
What did I miss?
Thanks
Jeff KingRe: First time compiling source
On Tue, Jan 15, 2008 at 02:34:12PM -0600, Chris Ortman wrote:
> then to check > which git > /home/chrisortman/bin/git > as expected > > however git --version still reports 1.5.2.5 > > What did I miss?
Is bash caching the location of git? Try 'type git' in that shell, or try running 'git --version' from a new shell.
-Peff
Chris OrtmanRe: First time compiling source
That was it, thanks.
On Jan 15, 2008 2:56 PM, Jeff King <peff@peff.net> wrote:
> On Tue, Jan 15, 2008 at 02:34:12PM -0600, Chris Ortman wrote: > > > then to check > > which git > > /home/chrisortman/bin/git > > as expected > > > > however git --version still reports 1.5.2.5 > > > > What did I miss? > > Is bash caching the location of git? Try 'type git' in that shell, or > try running 'git --version' from a new shell. > > -Peff >
Alex RiesenRe: First time compiling source
Chris Ortman, Tue, Jan 15, 2008 21:34:12 +0100:
> Up until today I've always run git off whatever debs come with ubuntu. > But if I'm going to try to do some work I figured I should be > compiling from source. > > To compile I did > git co -b current v1.5.3.8 > make > make install > > then to check > which git > /home/chrisortman/bin/git > as expected > > however git --version still reports 1.5.2.5 > > What did I miss?
The git in /usr/bin is stuck in hashed paths of your shell? For instance, bash remembers all the programs it managed to exec.