It is possible to update the $PATH to grab from /usr/local/bin/* (user stuff land) before /usr/bin/* (system stuff land). If you're comfortable using command line to manage code, editing the ~/.bashrc shouldn't be too difficult to manage.
Yeah, obviously. But the point is that if the presupplied git quickly becomes out of date, what's the point in Apple shipping it and it taking up disk space? The Apple-supplied versions of other OSS packages (e.g. Ruby) don't exactly set a good precedent.
How often is there a new feature and not just a bugfix in git? Honest question as I don't use git.
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...
Comments
It is possible to update the $PATH to grab from /usr/local/bin/* (user stuff land) before /usr/bin/* (system stuff land). If you're comfortable using command line to manage code, editing the ~/.bashrc shouldn't be too difficult to manage.
Yeah, obviously. But the point is that if the presupplied git quickly becomes out of date, what's the point in Apple shipping it and it taking up disk space? The Apple-supplied versions of other OSS packages (e.g. Ruby) don't exactly set a good precedent.
How often is there a new feature and not just a bugfix in git? Honest question as I don't use git.
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...