And I have an open pull request so that Snap apps can read the LXQt and Kvantum configuration to follow the chosen theme.
Now I need to receive automatic connection for the lxqt-support-core22, lxqt-support-core24 Snaps and for the future lxqt-support-core26.
What are the options to make this possible?
I don’t see any problems if I have to transfer these Snaps to someone, such as Canonical.
If you want an example of what I’m trying to make possible, it’s basically what happens in the video below, where I demonstrate how a Qt6 Flatpak app appears in Lubuntu, and how the Snap version of the same app appears in Ubuntu after all the changes I want to make.
I’ve been messaging with @Kyuyrii on matrix and I think I understand the particular request.
The kde-neon-6 snapcraft extension does many things designed to make snaps which use it (generally Qt snaps) function and integrate well with the host system. One of which is declare the kf6-core24 content interface plug which has default-provider: kf6-core24 in the resulting snap package’s meta/snap.yaml (WLOG, assuming base is core24). This content snap ensures the consumer snap integrates well on the KDE desktop.
The kf6-core24 snap is published by kde and, importantly, that content plug connected to the slot provided by kf6-core24 is auto-connected for any snap built using the kde-neon-6 extension.
Recently, @Kyuyrii extended the kde-neon-6 snapcraft extension to improve integration on LXQt, in addition to KDE. In particular, they made the kde-neon-6 extension now automatically add a content plug provided by the lxqt-support-core24 snap. This change shipped with Snapcraft 8.14 (see the Release Notes), and the PR to add it was https://github.com/canonical/snapcraft/pull/5917
Now, snaps built with snapcraft 8.14+ and the kde-neon-6 extension have both the kf6-core24 and lxqt-support-core24 plugs declared, as desired.
However, the problem is that the lxqt-support-core24 plug is not autoconnected, like kf6-core24 is. @Kyuyrii is the publisher of the lxqt-support-core{22,24} snaps, but would be fine with transferring ownership of them if necessary.
So the request is to make the lxqt-support-core22 or lxqt-support-core24 plug generated by the kde-neon-6 extension autoconnect, just like the kf6-core24 plug does. So I think this would require a store assertion on the slot side of the content plug lxqt-support-core22 and lxqt-support-core24, auto-connecting any connections where they are the provider. But I’m not certain how this works. I assume whatever was done to make content plugs autoconnect to slots provided by kf6-core24 would work here as well.
