Want Git Preinstalled On The Next OS X?
github.com
github.com
What Apple should really do is build a proper package management system. IMHO, that is a fundamental part of a modern operating system, especially one designed for use with F/OSS software.
As far as I've seen, apple will include the latest stable version of a tool per major upgrade (e.g. tiger, leopard, etc.). They'll keep it the same version until the next major one, without touching point releases. In terms of the principle of least surprises, it's actually the way I'd prefer.
The other post's advice for .bashrc is very good, it's what I do.
Then they should stop claiming that OSX is suitable for use as a server OS.
Seriously, apple only cares enough about servers/etc to have a complete solution for their other markets, such as small business & education.
I suspect they've got the same problem others do: a case of NIH, without the resources to invent it themselves.
Ugh.
And does git really use up that much space to be an issue? I imagine the problem is just conflicting binaries/libraries which can be fixed pretty easily in .bashrc...
You don't need the latest version of git for init, clone, add, commit, push, and pull to work.
1. download macports
2. double click an installer and click next a few times
3. type 'sudo port install git-core' wget http://kernel.org/pub/software/scm/git/git-1.6.1.2.tar.gz
./configure
make
sudo make install
tar xfz git<Tab>
cd git<Tab> $ mate ~/.profile
# add "/opt/local/bin:/opt/local/sbin:" to beginning of "export PATH"
save
I've personally seen it delete the data during a postgres update, and it regularly runs roughshod over config files, etc. It screws up installs all the time, which can be a nasty surprise since it doesn't clean up after itself properly (this happened to me when it put a non-functioning ssh in my path, leading to a bit of panic when I suddenly needed it urgently). It can't clean up obsolete, well, anything without the "force" option, spewing spurious warnings all over the place .. except when it turns out they weren't spurious and you find out it deleted something critical. It's slow as hell to list what you do have installed. The maintainers are sloppy and non-working packages sit in the repos for weeks at a time (hello, Erlang).
Like I said, it's better than nothing, but I don't think anyone should use macports for anything that could conceivably store any data you care about. You will probably need to nuke /opt and re-build everything from scratch periodically, so make good and sure there's nothing in there that you care about. However, if you use it with caution and bear in mind the necessity of a periodic rebuild, it can be a big help.
Which goes back to my point.
I can't code if everyone else is doing it in place of me. :P
I rebuild Python and Ruby every other month.
You don't need to muck with macports or anything.
Maybe with an install of Xcode. But it has absolutely no purpose whatsoever being installed by default.
Though I'm surprised OS X ships with SVN by default. FWIW, the version of SVN that ships is 1.4.4 (and it still hasn't been updated as of 10.5.6 or iPhone SDK for 2.2.1.
And Python.framework and Ruby.framework are installed to let you run other programs people write. Same reason you have Java, Tcl/Tk and all the ObjC/Cocoa frameworks. Having the frameworks != writing code.