[MacPorts] #52700: port rev-upgrade stumbles over -weak_framework library dependencies

[MacPorts]

#52700: port rev-upgrade stumbles over -weak_framework library dependencies
---------------------+--------------------------------
  Reporter:  RJVB    |      Owner:  macports-tickets@…
      Type:  defect  |     Status:  new
  Priority:  Normal  |  Milestone:
 Component:  base    |    Version:
Resolution:          |   Keywords:
      Port:          |
---------------------+--------------------------------

Comment (by fhgwright):

 I've run into a somewhat related problem with `rev-upgrade` and the
 `MacOSX*.sdk` ports.  I wasn't surprised to see errors with a given SDK on
 an older OS; I was somewhat surprised to see errors with a given SDK on a
 newer OS; and I was ''really'' surprised to see errors in some cases with
 a given SDK on a ''matching'' OS (10.7 and 10.10).

 Since the SDK ports are just verbatim copies of Apple's code with no port
 dependencies, it's clearly completely useless to apply the `rev-upgrade`
 processing to them at all.  At best this is just a waste of time, and at
 worst it creates false errors and perhaps useless "rebuilds".  For cases
 like that, what's needed is a port attribute to opt out of `rev-upgrade`
 altogether (essentially by pretending that they have no binaries).

 The weak-linking case is a little more complicated, since ports that fail
 to make the appropriate runtime checks for weak linking are genuinely
 broken by weak-linking failures, while ports that do make the appropriate
 checks should be able to take such failures in stride.  I don't think
 there's any automated way to tell the difference, so it would need to be
 another port attribute - one that specifies ignoring weak-linking failures
 without opting out of `rev-upgrade` altogether.

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