Snaps to invoke external processes

Gustavo Niemeyer gustavo.niemeyer at
Wed Nov 30 21:14:10 UTC 2016

Note snapctl exists for a few weeks only, while xdg-open is there for
several months. We couldn't have done that much earlier.

It's probably not a great first task for newcomers, because we need to
teach snapctl to work out of hooks first, so it traverses several layers.

There's a chance you might get Pawel excited enough to work on this soon,
after he's done with retries. He's been touching on related subjects.

On Mon, Nov 28, 2016 at 5:34 AM, Didier Roche <didrocks at> wrote:

> Le 25/11/2016 à 18:09, Gustavo Niemeyer a écrit :
> The role of xdg-open itself is already to open the URL with whatever
> tooling is available, so it sounds like we're making the issue more complex
> than it ought to be.
> I think we should reimplement xdg-open in terms of snapctl, and have snapd
> itself doing the hand-over to the local xdg-open tool after some basic
> sanity checking on the URL. That way we're not really asking for anything
> from the local system (no dbus service) while remaining completely portable.
> Ah, that was my fist implementation proposal which wasn't accepted at
> the time. Happy to see that our view converge now
> Gustavo, do you mind opening a bug for tracking this (and we can
> reference people who want to help/contribute to it) as it would be an
> easy first snapd contribution for newcomers?
> Cheers,
> Didier
> --
> Snapcraft mailing list
> Snapcraft at
> Modify settings or unsubscribe at:
> an/listinfo/snapcraft

gustavo @
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Snapcraft mailing list