Bug 47920

Yeah, good point.  We could add

[environment]
GDK_BACKEND=wayland

to weston.ini.

On Fri, Jul 20, 2012 at 7:58 PM, <bugzilla-daemon@freedesktop.org> wrote:

> https://bugs.freedesktop.org/show_bug.cgi?id=47920
>
> --- Comment #1 from Kristian Høgsberg <krh@bitplanet.net> 2012-07-20
> 18:58:08 PDT ---
> Yeah, good point.  We could add
>
> [environment]
> GDK_BACKEND=wayland
>
> to weston.ini.
>
> --
>
>
Perhaps you might still want to start with the X backend on some launchers
and wayland backend on others? Typically,
I guess if you want to explicitly set an env var that's not part of your
global environment, you'd run it from a terminal shell.
A user can use a quick wrapper script to do what they want and call that
from the launcher instead. Aside from that,
would it be feasible to have something like this? I'm not sure if it would
be sane or easy to parse something like this
but the idea is that you'd be able to set any number of arbitrary env vars
for each launcher (probably easier to just use a
wrapper script at this point).


[launcher]
icon=/path/to/icon.ext
path=/path/to/program
environment="ENV_VAR1=foo"
environment="ENV_VAR2=bar"

(In reply to comment #2)
> On Fri, Jul 20, 2012 at 7:58 PM, <bugzilla-daemon@freedesktop.org> wrote:
> 
> > https://bugs.freedesktop.org/show_bug.cgi?id=47920
> >
> > --- Comment #1 from Kristian Høgsberg <krh@bitplanet.net> 2012-07-20
> > 18:58:08 PDT ---
> > Yeah, good point.  We could add
> >
> > [environment]
> > GDK_BACKEND=wayland
> >
> > to weston.ini.
> >
> > --
> >
> >
> Perhaps you might still want to start with the X backend on some launchers
> and wayland backend on others? Typically,
> I guess if you want to explicitly set an env var that's not part of your
> global environment, you'd run it from a terminal shell.
> A user can use a quick wrapper script to do what they want and call that
> from the launcher instead. Aside from that,
> would it be feasible to have something like this? I'm not sure if it would
> be sane or easy to parse something like this
> but the idea is that you'd be able to set any number of arbitrary env vars
> for each launcher (probably easier to just use a
> wrapper script at this point).
> 
> 
> [launcher]
> icon=/path/to/icon.ext
> path=/path/to/program
> environment="ENV_VAR1=foo"
> environment="ENV_VAR2=bar"

Yeah, I think that would work.  Alternatively, we could just be a little better about parsing path=, so that you can specify arguments and environment varibles like this

  path=GDK_BACKEND=wayland gnome-terminal --full-screen

similar to what you'd do in a shell.

(hack hack hack)... which I just pushed to master:

commit d1936b9e2b352e93ace1b3609740ce4902b33a9e
Author: Kristian Høgsberg <krh@bitplanet.net>
Date:   Mon Jul 23 22:59:33 2012 -0400

    desktop-shell: Break command lines into env vars, executable and arguments
    
    We now support specifying environment variables and arguments in launchers
    by saying
    
      path=GDK_BACKEND=wayland gnome-terminal --full-screen
    
    for example.

>
>
> Yeah, I think that would work.  Alternatively, we could just be a little
> better
> about parsing path=, so that you can specify arguments and environment
> varibles
> like this
>
>   path=GDK_BACKEND=wayland gnome-terminal --full-screen
>
> similar to what you'd do in a shell.
>
>
Yes, that seems better.

Marking this as fixed.