[MacPorts] #61584: Use deployment target 10.16 on Big Sur

[MacPorts]

#61584: Use deployment target 10.16 on Big Sur
--------------------------+----------------------------
  Reporter:  ryandesign   |      Owner:  (none)
      Type:  enhancement  |     Status:  new
  Priority:  High         |  Milestone:  MacPorts 2.7.0
 Component:  base         |    Version:  2.6.4
Resolution:               |   Keywords:  bigsur
      Port:               |
--------------------------+----------------------------
Changes (by ryandesign):

 * cc: jmroot (added)


Comment:

 distutils is a part of python, so my guess is that python remembers what
 deployment target it was configured with and distutils complains if the
 deployment target used to build a module now (10.16) does not match the
 deployment target that was used to build python earlier (11.0). It
 probably just does a string comparison and is not aware of the fact that
 deployment targets 10.16 and 11.0 mean exactly the same thing.

 If that's true, then one solution would be to rebuild python with the
 10.16 deployment target. In my opinion it is wrong for distutils to care
 about the deployment target, so another solution would be to patch python
 (distutils) to remove that check or at least to fix it so that it
 recognizes that 10.16 and 11.0 are equivalent.

 I'm not sure what part of gdk-pixbuf2 is using python. It doesn't declare
 a dependency on a python port, so I guess it's using the macOS bundled
 python. So to benefit from any of our fixes it would need to switch to
 using a fixed MacPorts python.

 -----

 Instead of changing the deployment target to 10.16 for all ports on macOS
 11, we could provide an easy way for ports to individually opt into that
 behavior.

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