[PATCH weston 2/3] compositor: print a clear message when XDG_RUNTIME_DIR is not set

[Pekka Paalanen]

On Fri, 8 Jun 2012 01:05:34 +0000
"Eoff, Ullysses A" <ullysses.a.eoff at intel.com> wrote:

> Not sure why we're requiring XDG_RUNTIME_DIR to be set... isn't there another way to handle this more gracefully instead forcing Weston to exit?  I don't believe I've ever had problems running Weston when XDG_RUNTIME_DIR was undefined.
> 
> According to the spec at <http://standards.freedesktop.org/basedir-spec/latest/ar01s03.html>:
> 
> "If $XDG_RUNTIME_DIR is not set applications should fall back to a replacement directory with similar capabilities and print a warning message. Applications should use this directory for communication and synchronization purposes and should not place larger files in it, since it might reside in runtime memory and cannot necessarily be swapped out to disk."
> 

Hi,

yeah, I tried something like that in
http://lists.freedesktop.org/archives/wayland-devel/2012-June/003851.html
although for a different purpose, and the feedback told me to use
XDG_RUNTIME_DIR only.

Perhaps the confusing thing in the previous fallback was using the
current working directory, instead of a predefined list of ways to get
globally (or at least per environment) consistent paths.

Krh?


Thanks,
pq