This commit includes 218 port updates and 16 tweak updates after KDE framework
changes. Most of this 16 changes caused by:
- KF5Auth split into KF5Auth and KF5AuthCore, which ends in a lot of new
WANTLIBs
- Upstream changed some xdg paths from share/examples/***/xdg/ to
share/qlogging-categories5/, which ends in a lot of PLIST chages.
List of notable changes:
- Bump all kf5 shared libs.
- Use ">=${MODKF5_VERSION}" in all kf5 ports that all kf5 use the
latest version an update together. (Idea from Qt5).
- s/=+/=/ for LIB_*,RUN_* and BUILD_* in x11/kde-applications, hint by jca@.
- Update okteta to 0.26.3
- Update spectacle only to 19.04.3, latest version without hard wayland
dependency.
- Remove python2 support in cantor, python3 only!
- devel/kf5/kfilemetadata: switch to python 3 (TDEP only), by kn@
- devel/kf5/ki18n: switch to python 3, by kn@
- devel/kf5/kservice: switch to python 3, by kn@
- devel/kf5/kconfigwidgets: remove python module usage, by kn@
- devel/kf5/ktextigwidgets: remove python module usage, by kn@
Tweaks and feedback from landry@, amd64 bulk build and error reports by naddy@
Thanks a lot!
Follow the upstream recommendations for packagers and switch to
multi-packages:
devel/gettext -> devel/gettext,-runtime
devel/gettext-tools -> devel/gettext,-tools
(new) devel/gettext,-textstyle
This is the last kf5 that supports Qt5 5.9.
Highlights:
- Reworked and unbreak our doas(1) usage in kdesu
- Fix breeze-icons/oxygen-icons tests.
- Move all test results away from Makefile to port Makefile
- Fix baloo bulk issues (again and again - Thanks ndaddy@ for the report)
- Update KDE Frameworks to 5.51.0
-- Change examples handling and use @sample for all of them. Idea by
ajacoutot@. Discussed with ajacoutot@,sthen@,naddy@.
- Update our KDE Applications to 18.08.2.
-- Nothing special except okteta. They use there own version pattern
now. I set EPOCH.
- Update all devel/kf5 consumers there are effected by the examples handling.
-- kdevelop
-- krusader
-- tellico
-- yakuake
Thanks to landry@ for feedback and hints
This framework offers the possibility to create integrate services and actions
on any application without having to implement them specifically. Purpose will
offer them mechanisms to list the different alternatives to execute given the
requested action type and will facilitate components so that all the plugins
can receive all the information they need.
ok landry@
