a report from Anindya Mukherjee
qutebrowser needs to identify the version of chromium used in the QtWebEngine
build; this appears to not be easily available via QtWebEngine/PyQtWebEngine
API so it does this by attempting to parse the ELF .so file, however it does
not know about OpenBSD ports shared library versioning.
The fix used here is to search for the highest numbered .so file and use that.
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.
NB: this isn't the latest version (1.x is), however it dropped support for
(legacy) QtWebKit which results in:
"""
qutebrowser needs QtWebKit or QtWebEngine, but neither could be imported!
The errors encountered were:
QtWebKit: Unsupported legacy QtWebKit found
QtWebEngine: cannot import name 'QtWebEngineWidgets'
"""
