Age | Commit message (Collapse) | Author | Files |
|
|
|
|
|
|
|
that doesn't break every dbus using app
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* create a dbus.inc
* remove outdated dbi
* remove DEFAULT_PREFERENCE from 1.0.1
* dbus-glib still has both versions since 0.72 doesn't build for me
|
|
|
|
|
|
|
|
RFC: remove dbus 1.0.1<x>0.92 as a cleanup?
|
|
|
|
result in their site files
|
|
* cross.patch isn't needed anymore
* dbus-uuidgen is now run in the initscript instead of the postinst
|
|
|
|
|
|
|
|
|
|
|
|
* rebuild dbus and apps dependant on it
|
|
* people wanting the use the old-API dbus can use 0.23.x
* people wanting to use the new-API dbus should use 0.9x
* new-API glib bindings are provided via dbus-glib
|
|
|
|
|
|
and 'b27820d75a034508419598a68bcbe1342bcf2ee1'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Use require for the BitBake files within packages. In contrast
to the conf files the authors of these files expected these files
to be included.
|
|
|
|
|
|
|
|
* NOTE: this is not a solution, but just moves the memory corruption in to a non-segfault area
|
|
|
|
|
|
|
|
headers on their host system
|
|
|
|
bug #1494
|
|
|
|
- DEFAULT_PREFERENCE = "-1" in dbus_0.60.inc
- there is a small API change in dbus_bus_request_name()
|
|
|