-
-
Notifications
You must be signed in to change notification settings - Fork 909
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git on old Macs #32
Comments
Those appear to be archives of the Git source code, which isn't going to work for us. Maybe this page of downloads? http://sourceforge.net/projects/git-osx-installer/files/ |
It seems the latest version of the workshop-template give the right information: For OS X 10.8 and higher, install Git for Mac by downloading and running the installer. After installing Git, there will not be anything in your Couple of things:
|
Both yes and no on that last point. /usr/bin/git exists in 10.9+, but the
|
Does anyone know if the git-osx-installers add /usr/local/git/bin to the user's PATH, or must that be done manually? |
I just installed from http://sourceforge.net/projects/git-osx-installer/files/ and it installs to /usr/local/git, but it doesn't seem to modify your PATH, so users may have to do this manually. I also found that OS X didn't want to open the installer because it doesn't come from a trusted developer, you have to do the right-click > Open trick. So those are some things we might need to note. Other people have experience with that? |
The common way to install software on OSX is to use homebrew, I think it supports older versions of OSX too but I need to verify. That would be the perfect solution because with the same tool you can install also python, r, and whatever, there's heaps of packages. |
Most of our students do not know how to use the shell before our workshops, so installing things via homebrew is a bit much to ask of them. |
Agreed. |
@jiffyclub @ethanwhite I understand, but I thought the problem was that the students had to fix their PATH, which is even worse. |
At this point I really don't have a clear enough picture about what exactly people with versions of OS X older than 10.8 have to do. Unless someone here has access to a computer running 10.6-7 and can test things, we may have to wait until someone brings in a complete report from a workshop. |
@jiffyclub I might have some old macs in my lab, I'll do some tests and report back (be aware that my report could include "please upgrade" :-)) |
That'd be great, especially if they are really fresh. E.g., don't have Xcode or any command line tools or anything else installed. I really wish everyone would upgrade to at least a semi-recent OS, but sadly it's not an option at a workshop or with some managed equipment. |
On older mac homebrew requires a ~2GB download of XCode to just get started with homebrew, not gonna happen with shaky wifi. As @DamienIrving mentions this was fixed in the carpentries/workshop-template#134 and confirmed to work at a workshop in January. |
@jiffyclub, the user I installed it for was able to use it with no PATH modification, I've had to do this a couple of times in the past and I don't recall modifying PATH's. |
@jduckles, thanks for the report! We can probably close this, then. |
@jiffyclub Agreed, stick with the sourceforge links, not the kernel.org tarballs. |
Good. I've updated the wiki at the workshop-template repo to reflect this. |
This blog post talks about the problem participants often have using git on older Mac laptops. It offers this site as a solution, which is an archive of older versions git. I'm thinking we need a short guidance document to provide some instructions on how to use that repository of old Git versions. For instance, which versions match up with which releases of Mac OS X? What do you do with one of the files once you've download it?
The text was updated successfully, but these errors were encountered: