On Tue, 7 Nov 2017 19:42:42 +0000 Daniel Stone <[email protected]> wrote:
> Hi, > > On 3 November 2017 at 07:33, Pekka Paalanen <[email protected]> wrote: > > - when the current socket search fails, add one more place to look > > in: /run/wayland/$WAYLAND_DISPLAY with the default "wayland-0" if > > WAYLAND_DISPLAY is not set. > > NAK. It's a surprising change in behaviour which could catch people > who could reasonably expect other behaviour. It doesn't play well with > each session expecting to be able to create a socket called > 'wayland-0', which is separated by $XDG_RUNTIME_DIR being different > per session. Hi all, obviously the /run/wayland option would be most useful for systems that will only ever run a single graphical session at a time, in other words, appliances, maybe tablets and phones, but not traditional/desktop computers. For the record, I'd never have libwayland-server automatically create the /run/wayland socket. It seems concensus is turning towards supporting absolute paths in WAYLAND_DISPLAY, with the /run/wayland proposal being more controversial. As the latter can be trivially realized with the former, I think we have a conclusion: absolute path support is good. I would hope someone will resurrect the patch and send it, I can review it for one, I'd like another maintainer Reviewed-by on it as well, and please do explicitly post your Acked-by's for the patch. If the /run/wayland proposal is still really wanted, it can be raised again after we have the absolute path support in WAYLAND_DISPLAY. Thanks, pq
pgpkQuQIW3sgF.pgp
Description: OpenPGP digital signature
_______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
