[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:12 mojca]:
 > Steve, are you able to figure out how exactly stack fetches the sources?
 … I'm pretty sure there must be a way to convince stack to download stuff
 using some library from MacPorts. We just need to figure it out.

 The Haskell code is in the {{{http-download}}} package, which is part of
 {{{stack}}} and relies on Conduit:
 * http://hackage.haskell.org/package/http-download
 * https://github.com/commercialhaskell/http-download
 * https://github.com/commercialhaskell/http-
 download/blob/master/src/Network/HTTP/Download.hs

 This isn’t going to be reproducible with a MacPorts library.

 For the sources, see the variable {{{{defaultSetupInfoYaml}}} in
 https://github.com/commercialhaskell/stack/blob/master/src/Stack/Setup.hs
 . The default source yaml configuration is
 https://github.com/commercialhaskell/stackage-content/blob/master/stack
 /stack-setup-2.yaml .

 Example {{{ghc}}} download configuration:
 {{{
     macosx:
         7.8.4:
             url:
 "https://github.com/commercialhaskell/ghc/releases/download/ghc-7.8.4-release/ghc-7.8.4-x86_64
 -apple-darwin.tar.bz2"
             content-length: 129602990
             sha1: b7aff3983e9005b74d90c5a4fd7c837f9e752923
     …
 }}}

 I presume that source itself is downloaded from hackage, but I see links
 to fpcomplete’s S3 bucket fly by, so there’s some mirroring system for
 source lts and other resolvers.

 I agree that in principal it should be possible to mirror everything where
 you want it, but before signing up for all that you should assess how much
 work it would be to duplicate effort to do what {{{stack}}} already does.

 The {{{stack}}} issues page has some years-old requests for an offline
 mirror capability, but no one is working on it:
 https://github.com/commercialhaskell/stack/issues/1594

 I’m honestly not sanguine about the availability of the necessary
 resources to build all this within MacPorts, much less maintain it.

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