The snap kcm is a KCM Shell (Settings Module) for KDE. But, we can launch it independently, using the kcmshell6 binary. And that’s how I snapped it. I snapped the enitre kcmutils. It requires desktop-launch to launch the apps and snapd-control to change the permissions of snaps. This is using the snapd-glib api to communicate with snapd. I would like this to be in the stable KDE releases, before the 25.04 release, that’s why I am publishing this as a snap in the store. The snap manifest is here
After discussion with @pedronis we will need to know a bit more about the maintainability store for this snap before we can grant an interface as privileged as snapd-control. Could you please give us more context in this regard and clarify if it will be only maintained by you or it is planned to be maintained by the KDE community?
Other than @scarlettmoore mam, I don’t know anyone in KDE Community has experience with snaps. So, it’ll be probably only me for some time. I’ll also get support from the KDE Community, specifically Discover team, with regard to tests and CIs. But the core part is only on me. If @kottens can join me, that would also be great. This snap will be mostly an interim release. My main target is to integrate this into the System Settings, so, a deb package. But, this might also be handy in the all snap KDE Core as this would be the only way to manage the permissions there.
I don’t think you need to have a copy of kcmutils in this snap, it already depends on the kf6 runtime snap which brings kcmshell6
I don’t think it brings much value as a snap, here is my reasoning: (a) you’re not on Ubuntu Core, you’ll get the KCM in the system settings on your host session, (b) you’re on Ubuntu Core, and the KCM will then be part of the session snap
In both (a) and (b) scenarios I think you’re better off making the KCM part of the Plasma release. To me this looks like a better move than providing a snap.
Yes, that’s what my motive is also too. But, because we can’t have it in any major releases soon, specifically Kubuntu 24.10, as there is already feature freeze. So, I am getting this snap to the store for testing and taking feedbacks, look for bugs etc. After everything is properly tested, we can easily have it in the 25.04 release. Also, in the meantime, someone might be able to help with a deb package also.
I see the motive. Why not a deb in a ppa for the time being? The thing is, with the snap you’d be testing something different than what you’d want in production in the end.
I would still like to pursue with the manual review, as a deb will be limited to a particular release of a particular distro. A snap is very easier to maintain and opens the gate for a big userbase.
As per my credibility and these plugs being super privileged, I am a member of Snapcrafters and Ubuntu, and also, I have a months-old request for Star Developer which has a +1 from @alexmurray.
So, I would request @jslarraz to continue with the request.
just another recommendation that the best way forward here is to apply to have your work on kcm-snap incubated and then it will become part of KDE proper, most likely in the plasma group as a counterpart to the flatpak kcm… you can find out more information here:
https://community.kde.org/Incubator
doing this would enable translations, peer review, code checking and all other fantastic benefits that allow for for the best possible app. once included in KDE proper (which is not a lengthy process) the snap-kcm would be distributed everywhere plasma is . i’m personally happy to sponsor the application.
often what seem the direct route is usually not the best nor the quickest …
I’ll look into those after I get some inputs and feedbacks on it. There is no harm in having a snap of it, as it can be used anywhere, even in DEs where there is no permission manager.
if you get approval from the @policy-reviewers who have asked about maintainability because of the elevated privileges it uses. you suggest you will upstream to its rightful place and then are explicitly recommended to upstream first, by several KDE contributors, yet continue to assert your request but not heed any of the recommendations.
if you do somehow succeed, will then have added administration of transferring the snap app name registration to kde where it should be from the beginning. if you had begun the incubation process when you started this request, you would be much further along with a better quality app, closer to being in the hands of its intended audience.
As far as I understood, the right way to distribute this kcm would be within plasma as result of the incubation process. That will be the way it will be properly maintained by the KDE community. Thus, I’m not sure we should proceed with this request tbh.
It’ll be under the kde community, but this snap will also work in any release, any distro that can have snapd. Snaps don’t have any such tool to manage the permissions and this snap will help it.
As far as I know I think the policy is that only Verified Accounts or Star Developers can publish snaps with snapd-control. In addition, it is preferred that they already have an established userbase. But @holly should be able to clarify the process further here.
So I think the best way forward here is to get this officially under the KDE publisher and have it maintained there at this time.