On Qua, 2017-01-04 at 15:47 +0000, Sérgio Basto wrote:
Hi, My story with kde4-workspace continues , now I had upgrade to F24 , I choose just update to +1 to understand what is been retired from kde4 bits, I follow Rex Dieter work and I'm much very grateful to him . Like I already express , my goal is isolate kde4-workspace features and make it possible have kde4-workspace and kde5-workspace (plasma5) installed at same system, the rest of kde is kde of the system i.e. KDE 5.
Now the report of upgrade F23 to F24 [0] by itens :
1 - kde-runtime may provide org.kde.kuiserver [1], kde-runtime.spec have
%if 0%{?plasma5} && 0%{?fedora} < 24 %global kuiserver 1 %endif
may we extend life of kuiserver ? by change to 0%{?fedora} < 26 ?
2 - from `dnf list extras` I have kde-connect-kde4-ioslave.x86_64 1.0.1-1.fc23.1 kde-connect-kde4-libs.x86_64 1.0.1-1.fc23.1 so same happens on kdeconnect
%changelog
- Tue Dec 27 2016 Rex Dieter rdieter@math.unl.edu - 1.0.3-1
- kdeconnect-1.0.3 (#1408570), drop kde4 (compat) kioslave
before this commit we got #if 0%{?fedora} < 24 %global _with_kde4 1 #endif
can we extend life of kde4 kdeconnect (to f25) ?
3 - baloo [3] is a strange case, I had to build with %define plasma5 0
to not delete kde4 stuff and to build baloo and baloo-file packages , we just have baloo-libs in fedora proper ... how baloo works in plasma5 ? (it was working on F23 kde4-workspace)
4 - The major hacks for F24 was on kde4-theme-core split from plasma- workspace [4]
and add kdm-settings to kde-workspace and many others things from the official fedora package [5]
5 - for example kactivities works without any modification from Fedora official package which is built with plasma5 , because we have (new) package kactivitymanagerd , which provides /usr/bin/kactivitymanagerd ! As final note for what I see , upstream try keeps kde4 stuff healthy , in different components so seems , that kde4-workspace could exist for more time
Best regards,
[0] https://copr.fedorainfracloud.org/coprs/sergiomb/kde4for23/monitor/de tailed
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1249157
[2] https://src.fedoraproject.org/cgit/rpms/kde-runtime.git/tree/kde-runt ime.spec
[3] http://copr-dist-git.fedorainfracloud.org/cgit/sergiomb/kde4for23/bal oo.git/tree/baloo.spec?h=f24
[4] https://bitbucket.org/sergiomb2/kde4-fedora.v3/commits/a402bea8496eed 1681e9dda2eef2fe50f7acd0ba
[5] https://bitbucket.org/sergiomb2/kde4-fedora.v3/commits/d5f3151d2e91b4 0143b1059b04e485f615369a6e
This serious working :) I can control gtk+ themes
dnf install kcm-gtk --allowerasing Installing: kcm-gtk xsettings-kde Removing: kde-gtk-config
with the minor changes on baloo and kde-runtime (with kuiserver) patches in attach
I lost all kcm-akonadi(s) on kde4 system settings but all kdepim had changed to QT5 and works fine, I still can control it with akonadictl.
Also kcmshell5 --list works kf5-plasma and qt5-qtquickcontrols are installed . I may control kamera with kcmshell5 kamera, kcmshell5 works for kcm_sddm or kcmtrash for example, seems they work beautifully .
I had some scares but now I liked the final result of it, I even though in give up , but the main reason to try keep kde4-workspace , is all configurations that I need to migrate if I need to change , to other window manager .
Best regards.