Classic confinement request for io.github.prassamin.prasmoid

[northernlights]

To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.

---

• name: prasmoid
• description: The All in One Development Toolkit for KDE Plasmoids. Build, test, and manage your plasmoids with unparalleled ease and efficiency.
• snapcraft: https://raw.githubusercontent.com/PRASSamin/prasmoid/refs/heads/packaging/pkg/snap/snapcraft.yaml
• upstream: GitHub - PRASSamin/prasmoid: The All in One Development Toolkit for KDE Plasmoids.
• upstream-relation: I do their packaging
• supported-category: IDE
• reasoning: this is a development toolkit. It needs to write a system-wide configuration file to work, and additionally it offers self updating, overwriting itself in /usr/bin .

I understand that strict confinement is generally preferred over classic.

I’ve tried the existing interfaces

[store-requests-bot]

This request has been added to the queue for review by the @reviewers team.

[elisehdy]

Hello, this seems reasonable to me, but would you mind expanding a bit upon the ‘system-wide configuration file’ and how that interacts with the system? (#askForInfo)

[northernlights]

Hi, thanks for checking this.

And I’m sorry, I misspoke about the config file, let me correct. The command “prasmoid regen config” creates a config file in the current working directory (typically the directory where the plasmoid project is being worked on), which could be anywhere. So I could get away with the ‘home’ plug for that. And updating could be done through snap, telling users not to self-update when using snap.

I’m going to go with ‘strict’ confinement for now and see how that goes.

My bad. Thank you for your time.