We’re using a content interface to make userspace graphics drivers pluggable for deployment on Ubuntu Core.
We have a default provider of this content based on mesa:
And are using this with
At present, this autoconnects because I am currently the owner of both snaps. But for this interface we would want autoconnection regardless of the owner of the consumer.
@alan_g hey,
So just to confirm, the auto-connection is requested for the ubuntu-core-kiosk snap, right?
Thanks,
No, the other way around. Any consumer should be autoconnect to mesa-core20.
@emitorino, I’ll try another way to explain, it is like the gtk-3-themes interface. It doesn’t matter who owns a snap with the following fragment, it autoconnects:
gtk-3-themes:
interface: content
target: $SNAP/data-dir/themes
default-provider: gtk-common-themes
We want the same for graphics-core20
@alan_g - So just to clarify - what you are asking for is that the graphics-core20 content slot from the mesa-core20 snap be granted a global auto-connection declaration, such that any other snap which plugs this interface will auto-connect to it?
Can you detail what is provided by this interface and what purpose other snaps would use this for? Also can you commit to maintaining ABI stability for this content slot so that other snaps which come to depend on it will not suddenly break because its content changed in the future?
@alexmurray that’s right. ABI stability should be automatic: the mesa userspace is repackaged from the 20.04 archive. Both mesa and the archive are good at maintaining ABI.
Thanks for the update @alan_g - +1 from me for global auto-connect of the graphics-core20 content slot of the mesa-core20 snap. Can other @reviewers please vote?
+1 for global auto-connect of the graphics-core20 content slot of the mesa-core20 snap, from me too.
+2 votes for, 0 votes against, granted global auto-connect for the graphics-core20 content interface from the mesa-core20 snap. This is now live.