qt5-qtwebengine broken on OCLP systems

[Gandoon (Erik Hedlund)]

Sadly, similar to the ffmpeg* ports (see #70882), also qt5-qtwebengine @5.15.18 appears to be broken by the same mechanism (or so it seems). A rev-upgrade produces the following:

--->  Scanning binaries for linking errors
Incompatible library version: /opt/local/bin/ffmpeg requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/bin/ffplay requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/bin/ffprobe requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/lib/libavdevice.58.13.100.dylib requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/lib/libavfilter.7.110.100.dylib requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/libexec/ffmpeg7/bin/ffmpeg7 requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/libexec/ffmpeg7/bin/ffplay7 requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/libexec/ffmpeg7/bin/ffprobe7 requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/libexec/ffmpeg7/lib/libavdevice.61.3.100.dylib requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/libexec/ffmpeg7/lib/libavfilter.10.4.100.dylib requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/libexec/ffmpeg4/bin/ffmpeg4 requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/libexec/ffmpeg4/bin/ffplay4 requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/libexec/ffmpeg4/bin/ffprobe4 requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/libexec/ffmpeg4/lib/libavdevice.58.13.100.dylib requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/libexec/ffmpeg4/lib/libavfilter.7.110.100.dylib requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
Incompatible library version: /opt/local/libexec/qt5/lib/QtWebEngineCore.framework/Versions/5/QtWebEngineCore requires version 1.0.1 or later, but /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage provides version 1.0.0
--->  Found 16 broken files, matching files to ports
--->  Found 4 broken ports, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt:
 ffmpeg4 @4.4.5+gpl2
 qt5-qtwebengine @5.15.18
 ffmpeg @4.4.5+flite+gpl2+gpl3+jack+librtmp+nonfree+rav1e
 ffmpeg7 @7.1.1+flite+gpl2+gpl3+jack+librtmp+nonfree+rav1e+vmaf

Yet another issue to push upstream to OCLP perhaps? Unless there is an easy fix to allow the use of the older library?

Does anybody know if this is an actual problem, or if it only presents when checking the linking? So far, I have not run into any actual errors during the use of the components, but I would be interested to hear if anyone has run into actual problems.

[ryandesign (Ryan Carsten Schmidt)]

There is no "older library" for CoreImage. There has only ever been version 1.0.1. OCLP is lying by installing a wrapper library that claims to be version 1.0.0.

There isn't an actual problem in practice because modern macOS no longer checks library versioning like it used to.

Duplicate of #70882.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign:

There has only ever been version 1.0.1. OCLP is lying by installing a wrapper library that claims to be version 1.0.0.

This statement is wrong. My memory was hazy because it's been awhile since I wrote up my analysis in the other ticket.

What I should have said is all versions of CoreImage have been compatible with 1.0.1, even as their version has increased. OCLP's wrapper library claims to be version 1.0.0, hence anything that uses any version of CoreImage would not be expected to be compatible with it, hence MacPorts mentions that during its scan.