| bulldog68 | hi | 05:59 |
|---|---|---|
| bulldog68 | hi, i need a little help with content snap - when am trying to connect consumer snap plug to provider snap slot i get this error :- error: snap "core" has no "content" interface slots | 05:59 |
| bulldog68 | =L | 06:08 |
| jamesh | bulldog68: what command are you executing when you get that error? | 06:30 |
| bulldog68 | jamesh snap connect webengine-app:webengine513 | 06:31 |
| jamesh | bulldog68: if you only pass one argument to "snap connect", it will assume you are trying to connect to a slot on the "core" snap | 06:31 |
| jamesh | what is the other snap you want to connect to? | 06:32 |
| bulldog68 | webengine513 is name of provider snap | 06:32 |
| jamesh | you want to run something like "snap connect snap1:plug snap2:slot" | 06:32 |
| bulldog68 | oh let me try :) | 06:33 |
| jamesh | okay. You need to specify the names of the plugs and slots you want to connect | 06:33 |
| bulldog68 | okay | 06:35 |
| bulldog68 | am connected but i don't want users to do this command line stuff manually | 06:36 |
| bulldog68 | jamesh am connected but i don't want users to do this command line stuff manually | 07:00 |
| jamesh | bulldog68: in general, they shouldn't have to | 07:00 |
| bulldog68 | okay thanks :] | 07:01 |
| jamesh | bulldog68: if you're the publisher for both the plug and slot snaps, snapd should automatically perform the connection if the snaps are installed from the store (i.e. not from local files with "snap install --dangerous") | 07:01 |
| bulldog68 | okay | 07:01 |
| jamesh | If you need autoconnection in cases where they have different publishers, you can ask on the forum for a store assertion to be created | 07:02 |
| jamesh | this is what e.g. allows snapd to automatically connect apps to the gtk-common-themes snap | 07:02 |
| bulldog68 | hmm | 07:02 |
| bulldog68 | i have many snaps in store but content interface is new for me | 07:03 |
| bulldog68 | one more question, i have desktop-gtk3 in my provider snap and i want lauch my app using desktop-launch in consumer snap how we do that ? | 07:03 |
| jamesh | it doesn't happen automatically for snaps with different publishers because it can allow the slot snap to have code executed in the context of the plug snap | 07:03 |
| bulldog68 | jamesh what am trying to do is package my qt binary in one snap (consumer) and the runtime/libs etc in provider snap | 07:05 |
| bulldog68 | both snaps are mine and am testing them locally on my machine | 07:06 |
| jamesh | bulldog68: I don't know if there is a simple answer to that: you could probably modify the script to work with the locations you mount things into on the plug side though. | 07:06 |
| jamesh | bulldog68: that's basically what happens for snaps using desktop-gnome-platform | 07:07 |
| bulldog68 | in the plug side i added target: $SNAP/webengine513 but after connecting the directory wont appear in the plug snap | 07:08 |
| bulldog68 | in slot side i have read: - $SNAP | 07:09 |
| jamesh | bulldog68: the mount only happens within the snap's mount namespace: you won't see anything from a host system shell | 07:10 |
| jamesh | try doing "snap run --shell webengine-app" and then look in $SNAP/webengine513 | 07:10 |
| jamesh | (this starts a shell within the sandbox of the named snap application | 07:11 |
| bulldog68 | okay let me chk | 07:11 |
| bulldog68 | yes i can see things there | 07:15 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!