search

lakshminarayanaIOS / git-osx-installer

Automatically exported from code.google.com/p/git-osx-installer
0 stars 0 forks source link

"git: Command not found" after installation #31

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Install GIT using git-1.6.3.1-intel-leopard.dmg on Leopard (Intel)
2. Run "git" in Terminal.app

What is the expected output? 
I expect git to respond.

What do you see instead?
Command not found.

What version of the product are you using? On what operating system?
git-1.6.3.1-intel-leopard.dmg
OS X 10.5.6 Leopard (Intel)

Original issue reported on code.google.com by robert.w...@widescape.net on 23 May 2009 at 6:05

GoogleCodeExporter commented 8 years ago 
Git is installed in /usr/local/git/
Running "man git" works.

Original comment by robert.w...@widescape.net on 24 May 2009 at 10:20

GoogleCodeExporter commented 8 years ago 
Just found out, that no installer works for me. Same problem with all.

Original comment by robert.w...@widescape.net on 24 May 2009 at 10:25

GoogleCodeExporter commented 8 years ago 
OK, solved the problem. Just added /usr/local/git/bin/ to the PATH in ~/.login
But why didn't the installer do this for me?

Original comment by robert.w...@widescape.net on 24 May 2009 at 10:51

GoogleCodeExporter commented 8 years ago 
Do you see the file /etc/paths.d/git?  The installer put that, along with 
/etc/manpaths.d/git, to set your 
paths appropriately. It looks like your system took the manpath change, but not 
the paths change. Maybe 
you are overriding this system default behaviour somewhere?

Original comment by timchar...@gmail.com on 24 May 2009 at 3:28

GoogleCodeExporter commented 8 years ago 
The file /etc/paths.d/git exists and contains the correct path to git. Thanks 
for the hint. I'll take a look at all 
path configurations.

Original comment by robert.w...@widescape.net on 24 May 2009 at 3:50

GoogleCodeExporter commented 8 years ago 
Oh, this issue should be invalidated then. :-)

Original comment by robert.w...@widescape.net on 24 May 2009 at 3:51

GoogleCodeExporter commented 8 years ago

Original comment by timchar...@gmail.com on 24 May 2009 at 7:01

GoogleCodeExporter commented 8 years ago 
Try restarting Terminal. that was enough to fix it for me

Original comment by mattmaye...@gmail.com on 1 Jun 2010 at 8:24

GoogleCodeExporter commented 8 years ago 
Same here ... had to restart terminal.

Original comment by bwood...@gmail.com on 23 Nov 2010 at 2:49

GoogleCodeExporter commented 8 years ago 
Wow can't believe I have to restart my screen session I've had going for months.

Original comment by budli...@gmail.com on 3 Feb 2011 at 6:15

GoogleCodeExporter commented 8 years ago 
Thanks for all the posts.  I had the same problem .. until I read the responses 
AND restarted Terminal.  Thanks again.

Original comment by paul%tho...@gtempaccount.com on 2 Apr 2011 at 3:23

GoogleCodeExporter commented 8 years ago 
Restarting terminal resolved the issue

Original comment by b.sa...@gmail.com on 22 Jul 2011 at 11:40

GoogleCodeExporter commented 8 years ago 
drove me crazy for an hr until i found this post...Restarting the terminal 
fixed..

Thanks

Original comment by balu....@gmail.com on 28 Aug 2011 at 2:43

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
restarting terminal fixed it for me too

Original comment by jakedlev...@gmail.com on 10 Dec 2011 at 1:12

GoogleCodeExporter commented 8 years ago 
diddo, thanks

Original comment by saea...@microstrain.com on 29 Feb 2012 at 6:52

GoogleCodeExporter commented 8 years ago 
It would be great if the installer pointed out that you have to restart the 
terminal. This is just an utterly frustrating and entirely unnecessary bug.

Original comment by rtnw7...@googlemail.com on 13 Mar 2012 at 3:26

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I didn't expect people would not know to restart the terminal, I'll add a note 
in the README.  In reality, you don't have to restart the terminal, just your 
bash session. So opening a new tab would do the trick. Additionally, you could 
re-source /etc/profile.

I wouldn't call this a bug, it's behaving exactly as intended. The reason why 
it's installed to /usr/local/git is for ease of removal. I have pondered the 
possibility of symlinking in to /usr/bin, overwriting the Xcode installed git, 
but have been hesitant to do so... it feels messy. Still, this approach would 
remove the need to modify the terminal environment, and still provide a 
somewhat sane, easy way to uninstall git.

Original comment by timchar...@gmail.com on 13 Mar 2012 at 10:46

GoogleCodeExporter commented 8 years ago 
There is also /usr/local/bin

Original comment by jimpisaacs on 28 Feb 2013 at 4:22

GoogleCodeExporter commented 8 years ago 
/usr/local/git is such a weird place, I would think at least it would go to 
/usr/local/share/git then symlink back to to /usr/local/bin that doesn't 
interfere with Xcode, it makes more sense IMO.

Original comment by jimpisaacs on 28 Feb 2013 at 4:25