<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 25/11/16 17:09, Gustavo Niemeyer
wrote:<br>
</div>
<blockquote
cite="mid:CANySw1mavMvaaVxHBuV0_cuwjmtNN=1ob8Z6g4eH+J2Kqcp8sA@mail.gmail.com"
type="cite">
<div dir="ltr">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.
<div><br>
</div>
<div>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.</div>
<div class="gmail_extra"><br>
</div>
</div>
</blockquote>
<br>
I think this works, as long a we handle the failure cases ("no
xdg-open") sweetly.<br>
<br>
Mark<br>
<br>
<blockquote
cite="mid:CANySw1mavMvaaVxHBuV0_cuwjmtNN=1ob8Z6g4eH+J2Kqcp8sA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Nov 23, 2016 at 4:51 AM, Mark
Shuttleworth <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mark@ubuntu.com" target="_blank">mark@ubuntu.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
I think the port of snapd to a distro should handle
ensuring that<br>
"browse" works. How it does that is up to the port, as
long as the<br>
behaviour is clear it is easy to implement. We just to be
clear what<br>
expectaction a snap publisher can have. I would say
"snap-browse" is the<br>
command to use, and on *Ubuntu* that would be
snap-xdg-open.</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>