[MacPorts] #58934: 'stack' port does not build solely from a MacPorts mirror

[MacPorts]

#58934: 'stack' port does not build solely from a MacPorts mirror
-----------------------+-----------------------
  Reporter:  greyhare  |      Owner:  essandess
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.5.4
Resolution:            |   Keywords:
      Port:  stack     |
-----------------------+-----------------------

Comment (by greyhare):

 Basically, it just seems we're unlucky. {{{stack}}} doesn't support
 mirrors and hardcodes server names and root paths, and it's what the
 MacPorts maintainers chose to use.

 I need to test my Gentoo setup at work next week. I know they use
 {{{cabal}}}, and I know that {{{ghc}}}-dependent package updates used to
 be a huge PITA there but aren't these days. If I can get it running on
 Gentoo, then I can just run {{{jupyter-notebook}}} in a Gentoo VM via
 Fusion when I need to generate PDF output, which needs {{{pandoc}}}, which
 is the only reason I need any of this.

 My opinion of Haskell is pretty thoroughly in the gutter right now. Things
 need to not be useless without giving automated scripts unfettered access
 to an open Internet connection.

 Thanks for trying.

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