Theme Connector For Snaps classic confinement

[jamesh]

@gantonayde

Would it be possible to confirm that the naming convention which @galgalesh suggested above, i.e. gtk-2-theme- , gtk-3-theme- instead of gtk-theme- is the one needed? It is not a problem to split the themes and upload them separately, I just don’t want to register all possible names for no reason.

I was planning to just use gtk-theme- as the prefix for snap names, for two reasons:

1. When there is a matched set of GTK 2 and GTK 3 themes, they’re usually maintained by the same developers, and often released together as a set.
2. The XSETTINGS protocol exposes a single gtk-theme-name setting, rather than version specific settings.

We’ve got one test snap up on the store for testing: gtk-theme-traditionalhumaized. It doesn’t have the “greedy connection” snap declarations from the store yet, so it doesn’t yet demonstrate the auto connection behaviour we want.

@gantonayde

The thing which I cannot understand is whether the themes will be considered for auto-connection without the updated review-tools. Should I upload them now or it will be better to wait for the update?

I’d prefer you wait until we have the review tools checks in place. We want to make sure all theme snaps eligible to install are “safe”, and we don’t yet have a complete picture of what that means yet. It will probably include:

1. Contains the expected content interface slots
2. Shared content is valid (valid images, valid CSS, etc).
3. The snap does not provide any apps, daemons, or hooks

The last one is intended to ensure that installing the theme snap doesn’t result in code execution. We don’t want someone to package a popular theme and sneak in a cryptocurrency miner as a background service, for instance.