The docs about the content interface could use some improvement, but this my understanding of what has to happen.
- The
content
identifier specified by the theme snap’s slot must match thecontent
attribute of the consuming snap’s plug. If you don’t specify thecontent
value explicitly, then it will use the name of the plug and slot. So based on what themes the snap provides, this is something likegtk-3-themes
oricon-themes
etc. - There needs to be a “greedy” plug declaration in the store. This is already in place afaik, @jdstrand should be able to confirm this.
- You need to request auto-connection for the theme snap. @jdstrand; is this required for every theme snap?
- The theme snap needs to be installed.
When these conditions are met, all snaps using the theme plugs should auto-connect to the theme snap.
A system to automatically install the correct theme snap based on the system theme is still being worked on.