You can clone with
HTTPS or Subversion.
I run OS X Mountain Lion and have been experimenting with installing SciRuby. I followed the instructions in the Wiki in Build Instructions for OS X but found that they did not cover all the issues I ran into. When installing SciRuby (I cloned the repo then ran bundle install), I had issues with the following dependency gems (in addition to the gsl gem, which is already mentioned):
The problem with gtksourceview2 was that the pkg-config gem, invoked during installation, was unable to find libxml2, which is a dependency of gtksourceview2. This was due to a missing libxml-2.0.pc file in /usr/lib/pkgconfig. See here and here for more information on this. Basically Mountain Lion dropped a few .pc files from /usr/lib/pkgconfig for reasons I don't understand, even though the libraries (at least libxml2) are still packaged with Mountain Lion. The only way I was able to get gtksourceview2 to install was to brew install libxml2 and symlink the libxml-2.0.pc file that comes with it into /usr/local/pkgconfig using
brew install libxml2
sudo ln -s /usr/local/Cellar/libxml2/2.9.0/lib/pkgconfig/libxml-2.0.pc /usr/lib/pkgconfig
This directs gtksourceview to the libxml version installed via Homebrew rather than the system version-- not sure if that will cause any problems. I'm sure there's a cleaner way to fix this but I don't know what it is.
The issue with rmagick was that a simple brew install imagemagick seemed to create an incompatible imagemagick installation. I had to brew remove imagemagick and then brew install imagemagick --disable-openmp --build-from-source, as per this StackOverflow question.
brew install imagemagick
brew remove imagemagick
brew install imagemagick --disable-openmp --build-from-source
Anyway, just hoping to spare others on Mountain Lion my pain...
Hey @smackesey! I added your findings to the wiki as you can see.
If you ever find more problems (and solutions to them), feel free to add the information to the wiki. If you want, search for me on #sciruby at chat.freenode.net or send a message to the mailing list.
Hey @smackesey, could you close this issue? Thanks!