Added installing on OS X

[holgi]

This should be considered as a primer to get you started on using pygit2 on OS X. Since I only have one Mac, I could not verify this on more OS Versions and / or settings.

[carlosmn]

This would then require you to set the path every time you want to use something which uses pygit2. A more common solution should be to brew link libgit2 which makes libgit2 available through /usr/local/, which is the path where non-system-provided software and libraries are installed and where the build system expects to see it (and where python will look when it needs to load libgit2).

[holgi]

I know about the brew linkcommand, but I am not very fond of linking optional packages into /usr/local.

I tried the following to test the libgit2 and pygit2 installation:

• install libgit2 with homebrew
• create a new OS X user
• switch to this user
• create a new virtualenv with python3
• activate the virtualenv
• run pip3 install pygit2

This worked without any problem. I didn't need to run brew link, nor did I edit any path information. (Now I'd like to have a new unaltered mac to try this out)

[carlosmn]

I don't get what you mean by optional here. Everything in /usr/local is installed by the user/admin and cannot be necessary for the operation of the OS.

You likely didn't need to explicitly run brew link because brew did it automatically. It is not done for some libraries because they would interact with the system's own versions, but the point of brew is to put stuff in /usr/local so you can use it.

[holgi]

Sorry, you are completely right. I was looking in the wrong place (/usr/local/bin instead of /usr/local/lib). I shouldn't write something on Monday morning before my second coffee.

[jdavid]

Hello,

As I understand the PR has not been updated to take into account the @carlosmn comments, @holgi?

I would like to merge this...

[holgi]

I had the opportunity to try this on a new Mac with Yosemite installed (since my old one broke down). After installing Xcode and homebrew I could run the following commands without any problems:

brew update
brew install libgit2

and install pygit2 in a fresh virtualenv with

pip3 install pygit2

Maybe the stuff to export the libgit2 part could just be left out.

[jdavid]

yes I think so, just leaving out that part would be enough