[MacPorts] #71051: Macports should add a global "use_xcode yes" config option

[MacPorts]

#71051: Macports should add a global "use_xcode yes" config option
--------------------------+--------------------
  Reporter:  mouse07410   |      Owner:  (none)
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  base         |    Version:
Resolution:               |   Keywords:
      Port:               |
--------------------------+--------------------

Comment (by ryandesign):

 Replying to [comment:5 mouse07410]:
 > > The {{{use_xcode}}} variable exists so that ports that require Xcode
 can use it. If there are ports that require this to be set that haven't
 set it, individual bug reports should be filed for each of those ports
 >
 > True, but that is taking time and efforts, every time a port gets bitten
 by CLT incompatibility. It taxes (unnecessarily, IMHO) every port
 maintainer and users of that port. Plus, the time lag for discovery, time
 lag for discussion, time lag to incorporate the fix. All of which could be
 avoided if the {{{use_xcode}}} is added or move to (a) become **global**,
 and (b) **user-controlled**, rather than port maintainer-controlled.
 >
 > I'm advocating for turning the control of whether to use CLT or Xcode,
 to user.

 Right. What you're saying is: something in MacPorts doesn't work, and you
 want the freedom to fix it in such a way that only you benefit and other
 users don't. What I'm saying is that's not how MacPorts works. The purpose
 of MacPorts is that the way to build a particular software package only
 has to be discovered once, and that knowledge is then encoded into a
 portfile so that all users can successfully install it without needing to
 know the technical details of how it was done.

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