[PATCH wayland] RFC: Require WAYLAND_DISPLAY to be set instead of using wayland-0 as the default

[Daniel Stone]

Hi,

On 26 May 2015 at 10:26, Giulio Camuffo <giuliocamuffo at gmail.com> wrote:
> 2015-05-26 12:21 GMT+03:00 Pekka Paalanen <ppaalanen at gmail.com>:
>> I have a vague recollection this has been proposed before, but I can't
>> remember if there was any interest or discussion, nor what was the
>> original intent behind defaulting to "wayland-0".

Probably to match X11's behaviour of using :0 in the absence of a $DISPLAY.

>> Personally I'd be fine with this change, but I can't imagine what would
>> break if we did this.
>
> I think it is quite safe. All compositors need to export
> WAYLAND_DISPLAY anyway in case they use a different socket that
> wayland-0. What we could break is users starting apps, say, from a
> tty, but i think that's acceptable if we put a big warning in the
> release notes. It's not like they need to patch software to fix it.

Agreed. It would be nice if this just worked out of the box, but I
think the answer is maybe to work with the much better integration we
have today with, e.g., logind to push a default $WAYLAND_DISPLAY to
TTY/SSH users if that's desired.

Cheers,
Daniel