D-Bus Python Bindings 0.83.1 (2010-02-18)
=========================================
Fixes:
* fd.o #21172: avoid some deprecation warnings in Python 2.6
* fd.o #15013: add dbus.lowlevel.MESSAGE_TYPE_SIGNAL etc., for those who care
about message types at a low level
* When removing signal matches, clean up internal state, avoiding a memory
leak in long-lived Python processes that connect to signals from arbitrarily
many object paths (fd.o #17551, thanks to Marco Pesenti Gritti)
* When setting the sender of a message, allow it to be org.freedesktop.DBus
so you can implement a D-Bus daemon in pure Python (patch from Huang Peng)
This changes the buildlink3.mk files to use an include guard for the
recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS,
BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new
variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of
enter/exit marker, which can be used to reconstruct the tree and
to determine first level includes. Avoiding := for large variables
(BUILDLINK_ORDER) speeds up parse time as += has linear complexity.
The include guard reduces system time by avoiding reading files over and
over again. For complex packages this reduces both %user and %sys time to
half of the former time.
D-Bus Python Bindings 0.83.0 (2008-07-23)
=========================================
Features:
* Add bindings for DBusServer (thanks to Mathias Hasselmann, Huang Peng;
fd.o #14322, #15514).
* Omit the service's traceback from certain D-Bus errors: specifically, those
that were probably deliberately raised as part of an API. Subclasses
of DBusException that indicate programmer error can turn the traceback
back on if it seems likely to be useful.
Fixes:
* Don't emit spurious Error messages if libdbus gives object-path handlers
a message that isn't a method call (most likely because of binding to a
locally emitted signal, as in fd.o #14199).
* Make multiple filters added by Connection.add_message_filter work
(fd.o #15547, thanks to Huang Peng).
* Make the API docs build correctly when out-of-tree
* Require dbus 1.0 so we can get rid of DBUS_API_SUBJECT_TO_CHANGE
- Supports DESTDIR
- Accept Python 2.5
News:
* supplying reply_handler but not error_handler raises
MissingReplyHandlerException instead of MissingErrorHandlerException,
and vice versa (fd.o #12304, patch from Rene Neumann)
* Using non-recursive make for dbus/ directory should fix builds in some
environments (fd.o #12741)
changes:
-fixes
-dbus.Bus() deprecated
-ode for which Collabora is the only copyright holder is now under
the same permissive MIT/X11 license under which dbus core
is being relicensed
D-Bus Python Bindings 0.71 (24 July 2006)
==
- Binary modules are now installed in the correct directory
- Distutils exports the dbus and dbus-glib cflags
D-Bus Python Bindings 0.70 (17 July 2006)
==
- First release of bindings split
- Move to a distutils build enviornment
- It is possible to now specify sender_keyword="foo", path_keyword="bar" when
adding a signal listener
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.
For example, "make show-buildlink3" in fonts/Xft2 displays:
zlib
fontconfig
iconv
zlib
freetype2
expat
freetype2
Xrender
renderproto
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
