Commit affd8a7d authored by Simon McVittie's avatar Simon McVittie

spec v0.18 and D-Bus 1.5.6

parent 7afd5e97
D-Bus 1.5.6 (UNRELEASED)
D-Bus 1.5.6 (2011-07-29)
The "weird, gravy-like aftertaste" release.
In addition to new features and refactoring, this release contains all of the
bugfixes from 1.4.14.
Potentially incompatible (Bustle and similar debugging tools will need
changes to work as intended):
......@@ -12,6 +17,13 @@ changes to work as intended):
Other changes:
• D-Bus Specification version 0.18 (fd.o #37890, fd.o #39450, fd.o #38252;
Cosimo Alfarano, Simon McVittie)
· add the "eavesdrop" keyword to match rules
· define eavesdropping, unicast messages and broadcast messages
· stop claiming that match rules are needed to match unicast messages to you
· promote the type system to be a top-level section
• Use DBUS_ERROR_OBJECT_PATH_IN_USE if dbus_connection_try_register_object_path
or dbus_connection_try_register_fallback fails, not ...ADDRESS_IN_USE,
and simplify object-path registration (fd.o #38874, Jiří Klimeš)
......@@ -3,7 +3,7 @@ AC_PREREQ([2.63])
m4_define([dbus_major_version], [1])
m4_define([dbus_minor_version], [5])
m4_define([dbus_micro_version], [5])
m4_define([dbus_micro_version], [6])
......@@ -36,7 +36,7 @@ LT_CURRENT=9
## increment any time the source changes; set to
## 0 if you increment CURRENT
## increment if any interfaces have been added; set to 0
## if any interfaces have been changed or removed. removal has
......@@ -77,6 +77,13 @@
<date>29 July 2011</date>
<revremark>define eavesdropping, unicast, broadcast; add eavesdrop
match keyword; promote type system to a top-level section</revremark>
<date>1 June 2011</date>
......@@ -4118,7 +4125,7 @@
<entry><literal>'true'</literal>, <literal>'false'</literal></entry>
<entry>Since D-Bus 1.5.UNRELEASED, match rules do not
<entry>Since D-Bus 1.5.6, match rules do not
match messages which have a <literal>DESTINATION</literal>
field unless the match rule specifically
requests this
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment