Go-nuts Re: How Do You Uninstall Go1 For Mac

/ Comments off

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.) From: Is my Mac OS X operating system supported? Where can I find information about operating systems supported by Apple? Generally Apple does not officially acknowledge the end of support for Mac OS X operating systems.

Historically, Apple’s support has been limited to 2-3 recent operating system releases. When Apple releases security updates for Mac OS, operating systems with vulnerabilities that are no patched by Apple should be considered unsupported and out of compliance with the Mininum Security Standards for Network Devices (MSSND).

Go-nuts Re How Do You Uninstall Go1 For Mac

The current list of supported Mac OS X operating systems (as of 2014-10-30): OS X 10.8 'Mountain Lion' OS X 10.9 'Mavericks' OS X 10.10 'Yosemite' I'd say it's pragmatic to drop the N-5 version. 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.

Go-nuts re how do you uninstall go1 for mac

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.