We want to deprecate the use of mir-libs content snap as the provider of mir-libs content and consolidate it instead with mir-kiosk snap itself. This will be bit less confusing to users of mir-kiosk.
mir-libs content snap currently has Auto-connection enabled for its mir-libs slot. We would like mir-kiosk:mir-libs to have Auto-Connection enabled as mir-libs content snap has.
I’ve not looked into this yet, but wanted to quickly say that the auto-connection for the old mir-libs snap happened before the critical thinking regarding auto-connection across publishers and discussed elsewhere (if unfamiliar with that thread, it is best summarized in this video). As such, we should be evaluating this as a new request.
(or something similarly clear that it was built using 16.04 environment), then it would ok to grant auto-connection. Please see the links in my previous response if you have questions as to why this is required.
As a minor note, we’re improving the content interface so this may benefit from some changes in the near future. That said, we of course won’t break the way it currently behaves, so if you need the interface right away, that’s the way to go.
Again, +1, and thanks for addressing the versioning detail, @jdstrand.