** Also affects: snappy
Importance: Undecided
Status: New
** Description changed:
- Take the following corresponding slot definition:
+ Take the following slot definition:
slots:
shared:
content: shared
interface: content
read:
- /dir1
- /dir2
- Pair it with the following plug definition:
+ Pair it with the following corresponding plug definition:
plugs:
shared-files:
content: shared
interface: content
target: my-target
Note that the slot supports multiple sources, and the plug supports only
a single target. The result isn't particularly useful: first, <slot
snap>/dir1 is bind-mounted to <plug snap>/my-target, then <slot
snap>/dir2 is bind-mounted again to <plug snap>/my-target. So <plug snap
>/my-target is always <slot snap>/dir2.
I look at this interface and can't come up with a rational user
expectation for what _should_ happen in this case. Is what's currently
happening expected? How do we expect multiple sources to be useful?
** Description changed:
Take the following slot definition:
slots:
shared:
content: shared
interface: content
read:
- /dir1
- /dir2
Pair it with the following corresponding plug definition:
plugs:
- shared-files:
+ shared:
content: shared
interface: content
target: my-target
Note that the slot supports multiple sources, and the plug supports only
a single target. The result isn't particularly useful: first, <slot
snap>/dir1 is bind-mounted to <plug snap>/my-target, then <slot
snap>/dir2 is bind-mounted again to <plug snap>/my-target. So <plug snap
>/my-target is always <slot snap>/dir2.
I look at this interface and can't come up with a rational user
expectation for what _should_ happen in this case. Is what's currently
happening expected? How do we expect multiple sources to be useful?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636633
Title:
Content interface supports multiple sources, but only one destination
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1636633/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
