connecting a non-auto interface, automatically

[Claudio André]

2017-02-08 14:37 GMT-02:00 Olivier Tilloy <olivier.tilloy at canonical.com>:

> On Tue, Feb 7, 2017 at 3:43 PM, Simon Fels <simon.fels at canonical.com>
> wrote:
> Where can this be requested?
>
>
+1.

Sorry, this is a hijack.

I would like to see an interfaces revamp/discussion. E. g.:
- my snap is useless without process-control, but works without home [1].
The previous is mandatory, the later is optional [2].
- why not document if an non-auto interface is mandatory? And, as Olivier
said, a mechanism to say: a required interface isn't connected.

I am, as an user, interested in using **some** snaps as 1st class software:
a 'turbo' text editor, a better archiver, GIMP, ...
- No alien "home", no need to copy files around to open them.

Claudio

[1] it is ok if the user wants to copy files from/to $SNAP_DIRs.
[2] In fact, auto-connecting home might be a bad idea.

PS:
- extending this, what about a filesystem interface:
  - a text editor snap (or an archiver) can run confined without problems.
But, the user might want to open /etc/fstab or a file in a removable media.

Sorry if this is offensive, I REALLY apologize. Recently in planet GNOME we
was able to read about flatpak "FileChooser portal". To me, it seems to be
the needed solution.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20170208/e7314385/attachment.html>