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 migh
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
> sn
On 25/11/16 17:09, Gustavo Niemeyer wrote:
> 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 its
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 aft
I think the port of snapd to a distro should handle ensuring that
"browse" works. How it does that is up to the port, as long as the
behaviour is clear it is easy to implement. We just to be clear what
expectaction a snap publisher can have. I would say "snap-browse" is the
command to use, and on
Unless dependencies such as snapd-xdg-open can be named in the yaml, I could
show a dialog telling the user that they may need to install it. Naming
dependencies of snaps, however, as I understand it, defeats the purpose of
snaps as they're supposed to bake all the dependencies into themselves.
Le 22/11/2016 à 15:38, Gustavo Niemeyer a écrit :
> The problem is that snapd works in environments where the dependencies
> to make the browser-launcher work aren't available.
>
> The right fix is probably to make it a dependency of one of the debs
> that are always installed on a normal desktop s
The problem is that snapd works in environments where the dependencies to
make the browser-launcher work aren't available.
The right fix is probably to make it a dependency of one of the debs that
are always installed on a normal desktop system, whether snapd is there or
not. It's a very minimal p
On Tue, 2016-11-22 at 07:46 +0100, Didier Roche wrote:
> Le 22/11/2016 à 05:43, Spencer Parkin a écrit :
> > Well, actually, not unless the customer also installs snapd-xdg-
> > open. Why is it an add-on? Why not just make it part of snapd?
>
> I gues the idea was to keep it as a separate daemo
On 22/11/16 06:46, Didier Roche wrote:
> Le 22/11/2016 à 05:43, Spencer Parkin a écrit :
>> Well, actually, not unless the customer also installs
>> snapd-xdg-open. Why is it an add-on? Why not just make it part of
>> snapd?
>
> I gues the idea was to keep it as a separate daemon and have the
> i
Le 22/11/2016 à 05:43, Spencer Parkin a écrit :
> Well, actually, not unless the customer also installs snapd-xdg-open.
> Why is it an add-on? Why not just make it part of snapd?
I gues the idea was to keep it as a separate daemon and have the
implementation which can easily change.
The "why it'
Well, actually, not unless the customer also installs snapd-xdg-open. Why
is it an add-on? Why not just make it part of snapd?
On Mon, Nov 21, 2016 at 9:09 PM, Spencer Parkin
wrote:
> It's a miracle! It works! Now, for the first time ever, my users (all 0
> of them) can reach the help page b
It's a miracle! It works! Now, for the first time ever, my users (all 0
of them) can reach the help page by clicking on "help" from within the
app! Thanks, Didier. You're a real pal.
On Mon, Nov 21, 2016 at 12:08 AM, Didier Roche wrote:
> Le 21/11/2016 à 04:26, Spencer a écrit :
> > It's bee
Thanks for the explanation Didier. :)
I'll try to install that package and check if it works. However, I guess
this package is only available for Ubuntu users right? Does anybody know if
it will be available on other distributions? It makes sense to me that if
snapd is a cross-distribution package
Le 21/11/2016 à 09:30, Eloy García (PC Actual) a écrit :
> Hi Didier.
>
> My snap package (wallpaperdownloader) invokes xdg-open internally but
> it isn't working yet. Should I use a specific interface to accomplish
> that? This is the snapcraft.yml
>
Hey Eloy,
You need to have snapd-xdg-open pac
Hi Didier.
My snap package (wallpaperdownloader) invokes xdg-open internally but it
isn't working yet. Should I use a specific interface to accomplish that?
This is the snapcraft.yml
name: wallpaperdownloader
version: "2.3"
summary: Download, manage and change your favorite wallpapers from the In
Le 21/11/2016 à 04:26, Spencer a écrit :
> It's been a few weeks now, but last I heard, the snapcraft team was or did a
> sprint to address current limitations snaps have regarding the invocation of
> external processes. Specifically, it would be nice to launch the user's
> default browser with
It's been a few weeks now, but last I heard, the snapcraft team was or did a
sprint to address current limitations snaps have regarding the invocation of
external processes. Specifically, it would be nice to launch the user's
default browser with a URL, or let a snap invoke another instance of
18 matches
Mail list logo
