-
Notifications
You must be signed in to change notification settings - Fork 18k
build: drop support for OS X 10.6 #9511
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
Comments
FWIW, I also have a very old 10.6 machine around that I still use. However, I would be happy to just use 1.4 in perpetuity on that machine. |
Having thought about this more, I think we probably should This will give 10.6 user enough time to migrate and also 1.5 |
This isn't like we're dropping some old Linux version that people might still have in production. This is dropping support for an ancient desktop Mac, where Go 1.4 would continue to work. |
I've sent an email to golang-nuts, let's see. https://groups.google.com/forum/#!topic/golang-nuts/-ESF2OhZlBk |
This list of security updates, http://support.apple.com/en-us/HT1222, shows that last one for OS X 10.6 was 12 Sept 2013. It would be nice for Apple to say publicly that they are dropping support, but when there hasn't been a security update for over a year and known issues are out there I would consider support dropped. |
From this link:
I'd say it's pragmatic to drop the N-5 version. |
Speaking of which, can we drop support for 32-bit OS X builds too? When was the last time Apple sold a 32-bit Mac? Camlistore had to add a warning for Mac users because enough of them were finding themselves with a 32-bit Go installed on accident and then having problems, e.g. linking against a 64-bit sqlite. |
It's really useful to be able to do my 386 testing on my 64 bit OS X machine. |
That's valid. But we can at least stop distributing builds from http://golang.org/dl/ if they're useless and misleading for almost everybody. I'm fine with continuing to run a darwin-386 builder to keep it working for Go developer use cases. |
According to Twitter, it's been 7-8 years since Apple sold a 32-bit Mac: https://twitter.com/bradfitz/status/553298936832589825 |
... which includes this wonderful table: http://www.everymac.com/mac-answers/snow-leopard-mac-os-x-faq/mac-os-x-snow-leopard-64-bit-macs-64-bit-efi-boot-in-64-bit-mode.html |
+1 for being able to run 32bit binaries on the mac. I just used this this morning. |
Not distributing 32-bit packages for Mac SGTM. IMHO, as long as Darwin still supports running 32-bit |
I only want to remove them from the downloads page. |
On 9 January 2015 at 08:52, Brad Fitzpatrick notifications@github.com
SGTM |
given that 10.6 builder still shows ok now, I propose that |
I propose we don't explicitly unsupport it but don't worry about maintaining it. This is essentially the whole world's policy. |
So the question is when do we stop the OS X 10.6 builders?
Given that they are still passing for Go tip, I think we can keep them
until 1.5 is released.
|
They may be "passing", but in several cases that's just because they're skipping tests. It's the same reason that plan9 is "ok" on the dashboard. |
I agree that OS X is skipping some tests (notably the close on
exec and external linking issues) to pass all.bash, but as Go 1.5
is about to enter feature freeze, I think it's still feasible to maintain
the 10.6 builder passing until 1.5 is released. And then we can
stop the builder at the beginning of the 1.6 cycle.
The only thing that could affect 10.6 builders now is dynamic
library support. But it seems nobody is working on adding that
to Darwin in the 1.5 cycle. (I'm happy to be proved wrong on this
though.)
|
Rob and I discussed this, and we propose that for Go 1.5, we will say something along the lines of "The port to OS X 10.6 (Snow Leopard) is no longer actively maintained." That is, we won't go out of our way to delete it or break it, but we're also not going to make any attempt to keep it working or to fix issues specific to that version of OS X. I should add that there are no plans to stop supporting GOARCH=386 on later versions of OS X, as long as OS X will run the resulting binaries. Being able to run a 32-bit toolchain on 64-bit x86 systems is too nice to give up without a fight. |
As discussed in #9495, it might be time to end our support for OS X 10.6.
I'm trying to find Apple's policy on supporting older versions of OS X, but it appears they haven't published anything publicly. (Which seems outrageous to me, but whatever.)
The major concern, I believe, is that OS X 10.6 is the newest version of OS X that runs on pre-EFI macs (or something?). I think @robpike actually has one of these old machines.
The text was updated successfully, but these errors were encountered: