I recently went on a remove-qt5 binge on my personal devices. Doing that, I bumped into a problem - manjaro-settings-manager is installed by default and still uses it.
Long story short, I’ve now got a branch that builds it against Qt6. No AI involved ^^. I can’t post links yet though.
Ideally, it - or a version of it - would get upstreamed, but I’ve not contributed to Manjaro before so don’t really know the process. Looks like the GitLab is closed and previous aspiring contributors have been asked to create a thread in the forum, so, here I am.
I don’t know the process, either. Perhaps, if you have an account at some git host provider (gitlab, gitea, github doesn’t matter) you could use this for sharing. Another option would be sending by email
Thanks for looking! Happy to collaborate on any needed changes, or feel free to just take it as a base and directly fix anything that needs it. I did briefly test it locally, but nothing in-depth.
It does and I was thinking about shipping it for testing purposes. What about the KCM module? It still installs desktop files in /usr/lib/kservices5/, so I’m keeping it disabled for now.
I built separate packages for testing I may push to unstable here soon.
It appears KCM desktop files should go in usr/share/applications/ with a kcm_ prefix for the filename from what I can tell from other Plasma 6 packages.
OK, I just pushed 43e192cbd6c2213a6a7a64d3a803f074884cffe8, which fixes the .desktop file location (but leaves them prefixed msm_ rather than kcm_ - I’m not certain about that one yet). It also does s/kcmshell5/kcmshell6/
The issue was the SERVICES_INSTALL_DIR variable, which was coming from KDEInstallDirs in ECM, which is actually KDEInstallDirs5. For whatever reason, you can’t use KDEInstallDirs6 without qt5 installed, but we can just use KDE_INSTALL_APPDIR instead.
I think KDEInstallDirs6 was specifically intended to only be used as a transitional variable for qt5 compatibility, with the expectation that qt5 would become phased out, and that as such KDE_INSTALL_APPDIR would be the only used variable from there on.
There was a similar analogy with regard to the qt6-based KDE packages. Initially they all had the 6 suffix added so as to distinguish them from those using qt5. Then, the qt5-based stuff was renamed with a 5 suffix, and then at a yet later stage, the 6 suffix was dropped from the qt6-based packages.
Am I missing something in the manjaro-settings-manager-kcm-qt6 package function? Is there a cmake_install.cmake to use for it like the notifier packages?
Oh, whoops. Honestly I have no idea what files are even part of the KCM module–especially with the Plasma 6 changes. We haven’t packaged it for a long time. @LordTermor used to help me out, but he’s not very active at the moment.
Previously, the three .desktop files were in /usr/lib/kservices5/, and not included in the manjaro-settings-manager package: https://gitlab.manjaro.org/packages/extra/manjaro-settings-manager/-/blob/master/PKGBUILD?ref_type=heads#L87. I guess they need to be removed from there in the same way msm_notifier_settings.desktop and msm_kde_notifier_settings.desktop are being removed, to leave just the manjaro-settings-manager.desktop in manjaro-settings-manager-qt6?
Poking at it… I’m a gnome user and not very familiar with KDE, but I think the KCMs themselves are the .so files in /usr/lib/plugins, and they want to be placed only in manjaro-settings-manager-kcm-qt6 as well? I don’t know about /usr/lib/qt6/plugins/ vs /usr/lib/plugins/. We’re installing to PLUGIN_INSTALL_DIR.
The point of them as far as I can see is that they can be shown in the plasma kde settings dialogue and via kcmshell6… if they work as expected. It would be nice for KDE users if we got it working, but equally, I don’t think there’d be any shame in continuing to not build the -kcm package . The functionality is still accessible via manjaro-settings-manager.