[MacPorts] #61263: Linking errors in multiple haskell ports

[MacPorts]

#61263: Linking errors in multiple haskell ports
-------------------------------------------------+-------------------------
  Reporter:  nickgaya                            |      Owner:  neverpanic
      Type:  defect                              |     Status:  assigned
  Priority:  Normal                              |  Milestone:
 Component:  ports                               |    Version:  2.6.3
Resolution:                                      |   Keywords:
      Port:  hs-alex hs-cabal-install hs-happy   |
  hs-hscolour                                    |
-------------------------------------------------+-------------------------

Comment (by nickgaya):

 Looking around haskell.org I found a couple of bits of information.

 * https://www.haskell.org/platform/contents.html
 > However, from 8.8 onwards, the platform has moved to core-only-
 installers, as the current best practices for managing packages have
 shifted to "nixlike-sandboxed" rather than global installs.

 * https://www.haskell.org/platform/mac.html#osx
 >The recommended way to install the components of the mac platform is
 using ghcup to install ghc and cabal-install, and following the
 instructions at haskellstack.org to install stack.

 Based on this, what do you think about changing the {{{haskell-platform}}}
 port to be a "virtual package" with dependencies on {{{ghc}}},
 {{{cabal}}}, and {{{stack}}}? I'm not sure whether having a port that only
 exists as a collection of dependencies goes against the design philosophy
 of MacPorts. Another suggestion is for {{{haskell-platform}}} to be a no-
 op with a notice suggesting that users install the aforementioned three
 ports. For a point of comparison, see: https://github.com/Homebrew
 /homebrew-cask/pull/47908

 Since the {{{hs-*}}} ports are unsupported/broken, they should definitely
 get cleaned up too. Has there been any progress on that since
 https://github.com/macports/macports-ports/pull/5050 was closed in April?
 I may be able to help with some of the busy-work if someone can advise me
 on what steps are needed. I haven't been able to find documentation for
 how port deprecation/deletion works in MacPorts. Maybe the broken ports
 could be replaced with a placeholder message advising users to use
 cabal/stack to install Haskell packages instead?

-- 
Ticket URL: <https://trac.macports.org/ticket/61263#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS