Interfaces for Raspberry Pi imager

[popey]

@alexmurray

Anyway, +1 for udisks2 auto-connect, and +1 for use of block-devices but -1 for auto-connect of block-devices - whilst I appreciate this is required for the snap to function, this is a privileged interface and is too powerful to grant auto-connect of IMO - plus the snap could try and detect whether this was available and raise a dialog to the user to prompt manual connection of this interface in the case that it is not connected.

There’s a further issue here. A user on Solus alerted me to a problem with another snap (sosumi) where I use snapctl is-connected (interface) to prompt the user to connect a disconnected interface before continuing.

They get:

error: error running snapctl: Unknown command `is-connected'. Please specify one command of: get, restart, services, set, start or stop

Which is likely because they’re on 2.39.3 as Solus is outdated.

So do we also need to add an assumes: 2.43 to the snapcraft.yaml as an extra guard, to prevent people installing the snap when on <2.43? If so, this will be needed on all snaps which use snapctl is-connected?