[MacPorts] #65478: glib2, glib2-devel, glib2-upstream: only has a build dependency on python?!

[MacPorts]

#65478: glib2, glib2-devel, glib2-upstream: only has a build dependency on python?!
-------------------------------------------------+---------------------
  Reporter:  RJVB                                |      Owner:  mascguy
      Type:  enhancement                         |     Status:  closed
  Priority:  Normal                              |  Milestone:
 Component:  ports                               |    Version:
Resolution:  fixed                               |   Keywords:
      Port:  glib2, glib2-devel, glib2-upstream  |
-------------------------------------------------+---------------------

Comment (by ryandesign):

 MacPorts has long had the practice of using its own ports as dependencies,
 rather than using the versions of those programs provided by the OS. There
 have been exceptions to this practice, and over time, those exceptions
 have proven problematic and have exemplified why we use our own ports
 instead. Python is the latest example: some ports have made use of
 /usr/bin/python, but the oldest versions of Mac OS X that MacPorts runs on
 have such old versions of /usr/bin/python that they are too old in many
 cases, so many ports have already either used MacPorts python27
 unconditionally or have used a condition to use MacPorts python27 on old
 versions of Mac OS X and /usr/bin/python on newer versions. Some users
 have objected to being made to install multiple versions of python,
 especially python27 which is EOL, so when possible we usually choose to
 use a recommended version of python3x (as specified in the python
 portgroup) rather than python27. Now that Apple has removed
 /usr/bin/python as of macOS 12.3 and since /usr/bin/python3 is only
 available starting in macOS 10.15, it's yet another reason to avoid the
 use of /usr/bin/python and /usr/bin/python3 entirely, even on systems
 where it would work, and just always use a MacPorts python port for the
 sake of consistency of ports across OS versions. I imagine that was Ken's
 thought process when adding the python3x dependency to this port.

 The ticket is closed and any remaining discussions about whether or not
 ports should be depending on MacPorts python ports, their performance, any
 improvements that one could make to those ports or the portgroup, the
 differences between different dependency types and so forth should
 probably be held in a more-visible location, such as on the macports-dev
 mailing list.

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