[MacPorts] #56850: DesktopManager @0.5.3 is still broken after rebuilding it (was: DesktopManager @0.5.3 does not build with port 2.5.3 on PPC Tiger)

[MacPorts]

#56850: DesktopManager @0.5.3 is still broken after rebuilding it
-----------------------------+------------------------
  Reporter:  ballapete       |      Owner:  ryandesign
      Type:  defect          |     Status:  accepted
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.5.3
Resolution:                  |   Keywords:  tiger
      Port:  DesktopManager  |
-----------------------------+------------------------
Changes (by ryandesign):

 * owner:  (none) => ryandesign
 * status:  new => accepted


Comment:

 The symlinks pointing to build directories are unsightly and shouldn't be
 there, but they're not causing any problems and that's not why MacPorts
 says the port is broken and tries to rebuild it.

 The real problem is that the Desktop Manager program is linked to its
 internal framework incorrectly—it's looking for the framework in the wrong
 location, so the program crashes if we try to run it:

 {{{
 dyld: Library not loaded:
 /Applications/MacPorts/DesktopManager.framework/Versions/A/DesktopManager
   Referenced from: /Applications/MacPorts/Desktop
 Manager.app/Contents/MacOS/Desktop Manager
   Reason: image not found
 Trace/BPT trap
 }}}

 I believe this problem was introduced 11 years ago in
 [335139f88298873aa1b1b65aa5c7386ce33c0866/macports-ports] when the port
 was converted from a manual build process to the xcode-1.0 portgroup. It
 was probably not realized at the time that this port's Xcode project file
 uses custom values of `INSTALL_PATH` to link the program and the internal
 framework together with a relative path so that the application can be
 installed anywhere, and that the xcode-1.0 portgroup would overwrite that
 custom `INSTALL_PATH` with an inappropriate value that would make the
 program link incorrectly. The port's revision was not increased at the
 time this change was made, presumably because it was erroneously believed
 that the change would not be visible to users, so if you had installed the
 port prior to August 14, 2007, you would not have been affected by this
 problem unless you reinstalled the port, as you now have.

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