On 12/23/2016 01:32 PM, Zygmunt Krynicki wrote:
Wiadomość napisana przez Kyle Fazzari <[email protected]> w dniu
23.12.2016, o godz. 19:27:
Hey all.
I'm trying to figure out what the `content` attribute is for in the
content interface. The docs say "The content attribute specified of the
consuming snap (plug) must have a content attribute match in the
providing snap (slot)." However, I have two snaps, provider side looking
like this:
slots:
share-foo:
content: foo
interface: content
read: [/]
Consumer side like this:
plugs:
use-foo:
content: foo2
interface: content
target: /bar
These interfaces connect fine, and I can see the contents of the
This is a bug. We know about it but fixing was deferred till we can use the
assertion system to control it.
Currently you can connect things manually but it will not auto-connect.
Is there a launchpad bug for this?
Regards,
/tony
--
Snapcraft mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
