setuptools (it's used as a package locator but importlib.metadata in
newer Python core or the external importlib_metadata are preferred).
So drop the RDEP in that case (it's still kept for py27) and bump
revisions.
This avoids the following message where solid tries to observe /etc/mtab:
QKqueueFileSystemWatcherEngine::addPaths: open: No such file or directory
Denglisch tweak an ok tb, Danke!
Changelog:
https://kde.org/announcements/frameworks/5/5.99.0/
Port changes:
- Help FindInotify with ${LOCALBASE}/lib/inotify/
- This has no effect with current consumers but can help to find Inotify with
small adjustments.
- kimageformats backport (significant performance issue experienced when using
animated AVIF images)
- 350ce1b990460cb2178f369f22fe80803f5645f3
- 1190e53e9b69da6f9663ceb75c4813c5708b7cbd
- Tweak make files
- Enable Inotify in kcoreaddons and baloo
- Use CFLAGS and CXXFLAGS instead of CMAKE_CXX_FLAGS and CMAKE_C_FLAGS.
- Use MODCMAKE_LDFLAGS instead of CMAKE_EXE_LINKER_FLAGS
- Fix broken builds with CMake 3.23
Comment:
QtQuick module providing high-performance charts
Description:
The Quick Charts module provides a set of charts that can be used from QtQuick
applications. They are intended to be used for both simple display of data as
well as continuous display of high-volume data (often referred to as plotters).
The charts use a system called distance fields for their accelerated rendering,
which provides ways of using the GPU for rendering 2D shapes without loss of
quality.
Maintainer: Rafael Sadowski <rsadowski@openbsd.org>
WWW: https://api.kde.org/frameworks/kquickcharts/html/index.html
OK abieber@ Thanks
In all the cases I know of, wayland-protocols is used as build dependency only.
In the context of KWayland (devel/kf5), used to generate interfaces from
wayland-protocols XML files.
See: https://api.kde.org/ecm/find-module/FindWaylandScanner.html
Spotted by sthen@ Thanks
Information for inst:kwayland-5.87.0
Comment:
Qt API to interact with the wayland-client and -server
Description:
KWayland provides two libraries:
- KWayland::Client
- KWayland::Server
As the names suggest they implement a Client respectively a Server API for the
Wayland protocol. The API is Qt-styled removing the needs to interact with a
for a Qt developer uncomfortable low-level C-API. For example the callback
mechanism from the Wayland API is replaced by signals; data types are adjusted
to be what a Qt developer expects, e.g. two arguments of int are represented by
a QPoint or a QSize.
Maintainer: Rafael Sadowski <rsadowski@openbsd.org>
WWW: https://projects.kde.org/projects/frameworks/kwayland
OK semarie@
