[MacPorts] #41796: binary package download ignores macosx_deployment_target set globally

[MacPorts]

#41796: binary package download ignores macosx_deployment_target set globally
------------------------+--------------------------------
  Reporter:  william@…  |      Owner:  macports-tickets@…
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  base       |    Version:  2.2.1
Resolution:             |   Keywords:
      Port:             |
------------------------+--------------------------------

Comment (by william@…):

 Replying to [comment:2 ryandesign@…]:
 > … there's no particularly good or particularly well-supported reason why
 a user should ever change `macosx_deployment_target` within MacPorts.

 I think there are good reasons to want to build packages which can be used
 on older versions of Mac OS, and even though there's a variable defined in
 the Portfile reference which does achieve this effect when set in the
 global config file!

 If it is really the case, I'd suggest that macosx_deployment_target should
 be removed as a MacPorts variable. How can it be useful in any particular
 portfile if it is not useful when used globally? I am not actually
 suggesting that this is done, though, since that would make it harder for
 me to do what I'm doing (!), just wondering what the use-case is that
 means it is still there in macports!

 Something which catches the attempted use of binary packages when in fact
 the user's macports.conf means (through macosx_deployment_target or any of
 the other (many, as you say) configurations which would mean they “don't
 match”) and prevents their use (or just tells the user that she ''must''
 add the {{{buildfromsource always}}} in order to use whichever option it
 is, would be useful, I think. Should I open an enhancement ticket to
 suggest this away from these various other reports?

-- 
Ticket URL: <https://trac.macports.org/ticket/41796#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X