tl;dr: Vast majority of code will never notice the difference. Go ahead and get the HP now and start enjoying 7.10.2 You can always update to the point release when it comes out.Despite all the testing, GHC central noticed just a day before release that there was a regression with text literals in 7.10.2. It was possible to work around the issue via a change to the text package, and text-1.2.1.3 was released just today. Alas, there wasn't enough time to re-build and test the platform installers between then and now, so this release has text-1.2.1.1. There will be a point release (7.10.2.1) of the Platform this weekend or next with the updated text package.The issue does not result in incorrect code, only slow compilation times for very text literal laden code (as in thousands of literals), and slightly higher one-time construction cost at run-time. In full stack builds and many other test builds, these slow downs were inconsequential.
The Haskell Platform on Windows now provides the MSys2 tools. These tools are needed when installing packages that use conf-tools (generally rare). These tools are not automatically placed onto the PATH in order avoid troubles due to MSys2 tools which have the same name as a standard Windows tool (e.g., echo, find, dir).
If I have understood correctly, in the upcoming OS X 10.11 /usr/bin and
various other directories will be locked down hard, and no third party
software will be allowed there.
So perhaps the installer should be changed to install the binaries
elsewhere, such as /usr/local/bin?
– Harald
Mark Lentczner wrote:
> Haskellers, we are pleased to announce the release of
>
> Haskell Platform 7.10.2
> /get it here... <https://www.haskell.org/platform/>/
_______________________________________________
Haskell-Cafe mailing list
Haskel...@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Haskellers, we are pleased to announce the release ofHaskell Platform 7.10.2
[...]
I notice that the OS X version is still installing binaries in /usr/bin.
If I have understood correctly, in the upcoming OS X 10.11 /usr/bin and various other directories will be locked down hard, and no third party software will be allowed there.
So perhaps the installer should be changed to install the binaries elsewhere, such as /usr/local/bin?
Haskellers, we are pleased to announce the release ofHaskell Platform 7.10.2
[...]
Many third party packages already use /opt, e.g. /opt/haskell or /opt/haskell-platform. (See for example XQuartz or calibre.)
Uh, 11.0, I mean.
> So perhaps the installer should be changed to install the binaries
> elsewhere, such as /usr/local/bin?
>
> Mostly correct. I would argue against /usr/local though […]
Good point.
> Many third party packages already use /opt, e.g. /opt/haskell or
> /opt/haskell-platform. (See for example XQuartz or calibre.)
Given the current use of /Library/Haskell, /opt/haskell seems the more
consistent choice.
– Harald