[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:27 mojca]:
 > On 10.8 it still used the wrong git version:

 My best guess is that this is a simple {{{PATH}}} issue. (I searched the
 Haskell code and couldn’t track down where the {{{git}}} command is
 issued).

 For deprecated OS’s, one could:
 * Take this upstream and ask how to specify the specific {{{git}}}
 executable. My expectation is that the answer is to set {{{PATH}}}.
 * Modify the {{{PATH}}} in the appropriate {{{.env}}} phase, or adding an
 {{{export PATH=…}}} to a {{{system}}} command, and hop that it doesn’t
 break something else.

 Related is the observation, shared by others, is that setting {{{PATH}}}
 in a {{{.env}}} doesn’t always work for some reason, so this approach will
 require double-checking and care.

 Also I have to ask: those old SSL standards are quite insecure now. I
 personally wouldn’t have the confidence to use them, or recommend their
 general use. Has anyone documented the downside risks of taking these end
 runs around modern standards to continue to use unsupported OS’s, which
 themselves have numerous unpatched CVEs?

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