Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm trying to install Git on a mac. I found these instructions: crainbandy

But, I don't understand this bit.

1. Change directories to the mounted image
bash$ cd /Volumes/Git\ 1.6.4.4\ Intel\ Leopard/
bash$ ls
README.txt                    setup git PATH for non-terminal programs.sh
git-1.6.4.4-intel-leopard.pkg            uninstall.sh
bash$ ./setup\ git\ PATH\ for\ non-terminal\ programs.sh
2. Run the shell script (last line above)

Yep, they've given exact instructions. But, I don't know bash and I rarely use Terminal, so I need some help. Do I literally type in the part that reads README.txt? Do I literally type:

bash$ cd /Volumes/Git\ 1.6.4.4\ Intel\ Leopard/
bash$ ls
README.txt                    setup git PATH for non-terminal programs.sh
git-1.6.4.4-intel-leopard.pkg            uninstall.sh
bash$ ./setup\ git\ PATH\ for\ non-terminal\ programs.sh"

Do I need to change anything?

I don't want to mess anything up.

share|improve this question
add comment

2 Answers 2

up vote 5 down vote accepted

NO, do not literally type bash$ ls …. The part with bash$ is your command prompt. You have to type everything behind that. So, in your case:

cd /Volumes/Git\ 1.6.4.4\ Intel\ Leopard/
ls
./setup\ git\ PATH\ for\ non-terminal\ programs.sh

If that doesn't work or seem to complicated, do yourself a favor and install Git using Homebrew. Run this:

/usr/bin/ruby -e "$(curl -fsSL https://raw.github.com/gist/323731)"

… then wait until it finishes. Re-start your Terminal. Then run:

brew install git

And you're done.

share|improve this answer
    
hi slhck, Thank you for helping me. I understand about the $bash now. After inputting the line beginning ./setup\ git... I got this back: "The domain/default pair of (/Users/myname/.MacOSX/environment, PATH) does not exist Variable PATH in ~/.MacOSX/environment.plist changed from '/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/opt/local/bin' to '/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/opt/local/bin:/usr/l‌​ocal/git/bin' ~ /Volumes/Git 1.6.4.4 Intel Leopard /Volumes/Git 1.6.4.4 Intel Leopard Macintosh-2:Git 1.6.4.4 Intel Leopard bash$" Am I good to go? Thank you! –  Laxmidi Sep 22 '11 at 4:32
    
hi @slhck, I ran out of room in my previous comment. Is the fact that it couldn't find the domain/default pair a problem? If I close Terminal and the open it again and then type "echo $PATH" It gives me: "/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/git/bin ". My bash$ prompt looks like: "Macintosh-2:~ myname$. I'm not sure what the Macintosh-2 bit means. Thank you very much for your detailed instructions. I really appreciate it. I'm trying to learn as much as I can. –  Laxmidi Sep 22 '11 at 4:46
    
It looks like the installer fixed this for you. When git is in your path, you should be ready to go! Your personal bash prompt is something like <computer-name>:<folder> <your-username>. You could change this, but it's not necessary. It could look different on every computer, the important thing is that when reading tutorials, the only thing you enter is everything after the $. Are you having any problems with the installation? –  slhck Sep 22 '11 at 8:05
    
Thank you for the help! It worked. I installed Git in order to install Aptana. I should be all set. Sweet. –  Laxmidi Sep 22 '11 at 16:11
    
Sure, glad to help! Just post a new question if you have any problems! –  slhck Sep 22 '11 at 16:51
add comment

What they have shown is a transcript of their session, including what you type as well as the responses. So, in principle, the way to interpret it — if you don't already know what it means just from looking — is “Type the parts that aren't already on the screen”. Though, your prompt is likely slightly different from the “bash$” they show.

In that particular transcript, typing any of those lines completely would just result in a harmless error.

If you're interested in learning and you have even a vague feeling for how to read the stuff already (I suspect you do since you e.g. recognized the README.txt part probably isn't to be typed), then I think it would be not too dangerous for you to just go ahead and try figuring it out for yourself.

You could also follow any old "getting to know the Unix/Linux command line" tutorial for a bit until you know how to read prompt-vs-command-vs-output and what "cd" does, then work on this.

share|improve this answer
    
Hi @Kevin Reid, Thank you for the explanation and encouragement. I've got a lot to learn. This a crawl before you can walk situation. Thanks. –  Laxmidi Sep 22 '11 at 4:47
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.