spec: Clarify that unix:tmpdir may create unix:path sockets even on Linux

Signed-off-by: Simon McVittie <smcv@collabora.com>

diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
index 27c849ce34f4f59be42146fe2ac1b3c521c6c39f..62c8e89df7aa8e587bd17546b61f3ae4db4f2ed3 100644 (file)
--- a/doc/dbus-specification.xml
+++ b/doc/dbus-specification.xml
@@ -3728,7 +3728,12 @@
               The same as "dir", except that on platforms with
               abstract sockets, the server may attempt to create an
               abstract socket whose name starts with this directory instead
-              of a path-based socket. This key can only be used in server
+              of a path-based socket.
+              The server is not required to create an abstract socket, even
+              on platforms that support it: treating "tmpdir" as being
+              equivalent to "dir" is a valid implementation, and recent
+              versions of the reference implementation of D-Bus do this.
+              Like "dir", this key can only be used in server
               addresses, not in client addresses; the resulting client address
               will have the "abstract" or "path" key instead.
             </entry>