[MacPorts] #25558: ghc: update to latest version

[MacPorts]

#25558: ghc: update to latest version
--------------------------------+-------------------------------------------
 Reporter:  jwiegley@…          |       Owner:  macports-tickets@…                   
     Type:  update              |      Status:  assigned                             
 Priority:  Normal              |   Milestone:                                       
Component:  ports               |     Version:                                       
 Keywords:                      |        Port:  ghc ghc-devel                        
--------------------------------+-------------------------------------------

Comment(by kitchen.andy@…):

 Replying to [comment:71 cal@…]:
 > In a discussion in IRC, Brandon suggests we stick to what is shipped in
 the Haskell Platform package, as this is what upstream encourages to ship.
 This would mean installing ghc 7.4.1 and updating a number of other
 packages at the same time:
 > It seems those updates would be pretty straightforward.

 Hi Cal,

 From a utilitarian perspective I don't think tracking the Haskell Platform
 is the best use
 of resources, basically I think what is most sorely missing is a high
 quality package that
 tracks the normal ghc releases with some patches to keep things ticking
 along.

 I don't see the logic in holding back a bugfix release, a large virtue
 of a package management system with auto updating is that bugfixes
 can be pushed down stream quickly and easily.

 I see three basic demographics, people who need nothing more than
 the platform can use the official .pkg releases. People who develop ghc
 can compile straight form source tarballs, possibly using the macports
 ghc as a bootstrap compiler. Which leaves people in the middle who need
 a high quality GHC release for development where bugs are fixed reasonably
 quickly.

 One major benefit of the haskell platform is the stable base it provides
 and I think that this is best serviced by the haskell platform .pkg
 releases.
 The macports ghc is going to be linked against different libraries
 and compiled by a different compiler, so this removes one of the major
 benefits of the haskell platform.

 I think that a future project to closely mirror the haskell platform in
 macports
 is an ok idea, but should be low priority because there is already a
 reasonably
 high quality haskell platform release.

 My suggestion would be to drop ghc-devel, make the ghc package track
 the normal stable releases and add ad new hs-platform-ghc that conflicts
 with ghc that can be kept down at whatever the platform release is.
 We can also hold off patching the hs-platform-ghc so that users can be
 sure exactly what bugs they will get too.

-- 
Ticket URL: <https://trac.macports.org/ticket/25558#comment:74>
MacPorts <http://www.macports.org/>
Ports system for Mac OS