Port to Plasma 6

[Kishore96in]

Tested on Arch Linux, and so far it seems to be working fine.

I have also updated the shell scripts for installation, but haven't tested them so far. They now depend on jq and on qtdiag6 (the latter being provided on Arch Linux by the package qt6-tools).

[Kishore96in]

@guiodic , re. https://github.com/domschrei/krunner-symbols/issues/25#issuecomment-2037558457, can you clarify

1. Which distribution are you using?
2. How did you install this plugin?
3. Which features don't work in the port?

It seems to work fine on my system:

[guiodic]

Yes, I had to reboot to get it working, strangely enough restarting only krunner was not enough.

[Kishore96in]

Dependency information is now updated in the README for Arch Linux, but not for the other distros (Fedora, openSUSE, Debian).

[rochacbruno]

+1 waiting for it to get merged

[Termuellinator]

I took the liberty to create a plasma6-runners-symbols-git AUR package based on your port_kf6 branch @Kishore96in while we wait on merging this PR :) I hope that this is OK for you, i'll switch over to this repo once it got merged. If you object to this, i'll delete the package again of course!

[reidprichard]

+1, was able to build and install on OpenSUSE Tumbleweed after installing a million KF6 libs.

[Niru2169]

+1, was able to build and install on OpenSUSE Tumbleweed after installing a million KF6 libs.

Dude please tell me which ones you had to install

[reidprichard]

I'm not sure this is an exhaustive list, or that all of these were for this one thing, but here's my best attempt. This was a lot of trial and error of trying to build, searching for the missing deps, and install my best guess. For example, it said it needed kf6runner, so I searched for kf6 and grepped "runner", leading me to kf6-krunner-devel. I expect this process will be necessary on other systems with potentially different package names, or for the packages that I may have missed here. But here's the list:

sudo zypper install --recommends -t pattern devel_qt6
sudo zypper install kf6-ktextwidgets-devel kf6-krunner-devel kf6-kservice-devel libplasma6-devel

Here are all the packages I have installed that I think might be relevant (on the Plasma side; I think the tutorial covered all the C deps):

i  | kf6-kconfig-devel                      | KConfig Development files                                                   | package
i  | kf6-kcoreaddons-devel                  | Utilities for core application functionality and accessing the OS           | package
i  | kf6-ki18n-devel                        | KDE Gettext-based UI text internationalization                              | package
i  | kf6-kpackage-devel                     | Non-binary asset user-installable package managing framework                | package
i+ | kf6-krunner-devel                      | KDE Framework for providing different actions given a string query          | package
i+ | kf6-kservice-devel                     | Plugin framework for desktop services: Build Environment                    | package
i+ | kf6-ktextwidgets-devel                 | KDE Text editing widgets: Build Environment                                 | package
i  | kf6-kwindowsystem-devel                | KDE Access to window manager: Build Environment                             | package
i  | kf6-sonnet-devel                       | KDE spell checking library: Build Environment                               | package
i+ | libKF5Plasma5               | Plasma framework - core libraries                                              | package
i  | libPlasma5Support6          | plasma5support library                                                         | package
i  | libPlasma6                  | Plasma 6 core libraries                                                        | package
i  | libplasma6-components       | Plasma QML components                                                          | package
i+ | libplasma6-desktoptheme     | Desktop theme files usable by Plasma 5 and Plasma 6                            | package
i+ | libplasma6-devel            | Plasma library and runtime components                                          | package
i  | libPlasmaActivities6        | Library for Plasma Activities support                                          | package
i  | libPlasmaActivitiesStats1   | Library for KDE's Plasma Activities support                                    | package
i+ | plasma-framework            | Plasma library and runtime components based upon KF5 and Qt5                   | package
i+ | plasma6-workspace-libs      | The KDE Plasma Workspace Components                                            | package

I'd start with those marked i+, as those are the ones I have manually installed. Good luck!

[Niru2169]

+1, WORKSSSS on Tumbleweed for me as well TYSM❣️ Thanks @reidprichard ! I got some package conflicts; looks like I had some version 5 packages

[paul]

Here's the package list for building on Fedora 40:

dnf install cmake extra-cmake-modules kf6-ki18n-devel kf6-kservice-devel kf6-krunner-devel kf6-ktextwidgets-devel gettext qt6-qtdeclarative-devel qt6-qt5compat-devel libplasma-devel

The last two are new, the ones before that are s/5/6/.

[northeastprince]

@domschrei can we get this merged?

[domschrei]

I apologize for the long radio silence. Unfortunately, over the last months there was too much other stuff going on for me to look after this project and participate in discussions in any meaningful way. It's gotten better now :)

A related problem is that I'm on Debian, with Plasma 6 nowhere to be seen (AFAIK), so I can't really test it myself. More generally, I'm wondering about how to go about the transition period while some users are still sticking with Plasma 5 for a while, since the changes to the Plugin appear to be breaking ones. Perhaps I'll integrate this fork as a separate branch while keeping the master branch on Plasma 5 until Plasma 6 is more widely used?

I hope I'll soon get around to set up a KDE Neon station/VM somewhere to test the fork myself and then update the documentation accordingly (also with the dependencies you found).

Thanks everybody, in particular @Kishore96in , for all the efforts!

[Kishore96in]

More generally, I'm wondering about how to go about the transition period while some users are still sticking with Plasma 5 for a while, since the changes to the Plugin appear to be breaking ones. Perhaps I'll integrate this fork as a separate branch while keeping the master branch on Plasma 5 until Plasma 6 is more widely used?

An alternative would be to tag a final version that is compatible with Plasma 5 (you can mention it in the README) and then make the master branch Plasma 6 compatible. That might be simpler if you don't plan to make any other changes to the plugin in the near future.

[domschrei]

For now, I added a new branch (plasma6) and linked to it from the master README. The branching will help if I want to push fixes or features to the code regardless of the Plasma version.

I haven't been able to test Plasma 6 myself yet – when doing so I'll be able to add a new release and consequently update the installation script that pulls the last release.