[PATCH wayland 2/2] support specifying custom directories for the client and server

[Jussi Laako]

On 19.11.2014 12:56, Pekka Paalanen wrote:
> I have very hard time deciding if we should allow the environment to
> overwrite the server and client assumptions on where the socket is. It
> would be easier for me to accept new API functions that operate with
> absolute paths or existing fds explicitly, but those of course require
> both servers and clients to be written to use them.

A bit tricky part in current Weston is case where you use 
wayland-backend. In this case Weston is client to another Weston and in 
addition server providing a socket to it's client. In this setup the 
server is sort of proxy between lower level server and the client.

Since both instances solely use XDG_RUNTIME_DIR, the wayland-backend 
client weston is trying to connect to a socket there are create a new 
socket with same name in the same place...

The change is intended to allow a way to tell this second weston where 
to look for the client socket and where to place the server socket. 
Usually these two are not the same place...