Ah, it is a historical artifact, now enshirned in the build tools. GHC central produced an installer package that put the compiler in /Library/Frameworks/GHC.framework (which is sort of the "correct" place on Mac OS X). HP then added an installer package that put stuf in /Library/Haskell (also "correct" by Mac OS X standards - see /Library/Python etc...) The HP then included a meta-package that installed both of those.
Now that the HP build builds the GHC portion from the bindist, I suppose I could configure it all to be under /Library/Haskell - though that would now deviate from how Python and Ruby were set up by Apple (they have dual prefexes one for libs one for interpreter). The only benefit to having untied releases is that in theory, if, say, HP 2014.2.0.0 and HP 2014.4.0.0 both used the same compiler (7.8.3), then one could have them both installed at the same time - which would benefit perhaps a few developers who want to back test against three or more HPs. The downside of tying to the HP release in such a case, is that the duplicate GHC portion is another ~750MB. (Side comment: Dang our release is large. We install over 1GB per release!)
_______________________________________________ Haskell-platform mailing list Haskell-platform@projects.haskell.org http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
