[MacPorts] #72582: A MacPort update failed. The installer couldn't identify the correct Xcode path

[MacPorts]

#72582: A MacPort update failed. The installer couldn't identify the correct Xcode
path
----------------------------+--------------------
  Reporter:  scrutinizer11  |      Owner:  (none)
      Type:  defect         |     Status:  new
  Priority:  Normal         |  Milestone:
 Component:  base           |    Version:
Resolution:                 |   Keywords:
      Port:                 |
----------------------------+--------------------

Comment (by ryandesign):

 Replying to [comment:2 scrutinizer11]:
 > Ok, thanks for your response. I was suspecting it, however, aren't there
 ways to quote the path?

 We could spend time fixing the MacPorts build system to work with paths
 with spaces. But you would encounter the same problem when actually trying
 to use MacPorts to build anything. See #54368. The path to the MacPorts
 source code also can't contain spaces. See #35910.

 > I have MacPorts on another machine, running a different macOS version
 with Xcode containing spaces in its name, but updating worked there.

 Not sure why without more info. One hypothesis: Very old versions of macOS
 would use more components from the command line tools than from within
 Xcode and so wouldn't be affected by the Xcode path.

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