[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 essandess):

 Replying to [comment:16 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.

 No, it’s what {{{pandoc}}} and nearly the rest of Haskell world chose to
 use, and we’re just following a build plan that’s robust and works:
 https://github.com/jgm/pandoc/blob/master/stack.yaml

 > 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.

 It’s still not clear why the pre-built {{{pandoc}}} binary isn’t in your
 mirror. You shouldn’t need {{{stack}}} at all.

 > 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.

 There’s an issues page to take that discussion:
 https://github.com/commercialhaskell/stack . Also, as mentioned above, the
 access isn’t unfettered, but laid out explicitly in
 https://github.com/commercialhaskell/stackage-content/blob/master/stack
 /stack-setup-2.yaml .

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