[SyncEvolution] synchronizing gdbus source and its copy in SyncEvolution

Hello Marcel! We have released SyncEvolution 1.0 alpha 1, based on a modified copy of the gdbus source code. The patches include several bug fixes and some extensions that we needed in SyncEvolution. Attached is the complete patch series - better late than never, right? ;-} One observation that we made on Moblin which might be of interest to you and the obexd team: gdbus conflicts with dbus-glib, which is invoked indirectly by the libecal/ebook in Moblin and (soon) Evolution 2.30. As a workaround we are using a private libdbus connection in gdbus, because that was easier than waiting for a fix in libecal/ebook (Moblin Bugzilla #8460). Regarding the name "gdbus": I have seen it also getting used for some D-Bus support code that is going to be merged into glib. Now a Google search mostly brings up hits for that other project. Moving gdbus patches between upstream and SyncEvolution is automated with some scripts in our "build" directory. I've done some trial runs, but we'll have to see how this works out in practice, in particular when you do not merge patches as they are. Because this could be problematic, I haven't cleaned up the patches despite some minor white space issues reported by "git am" and a partly faulty vsprintf() commit (fixed in a later commit). Please let me know how you want to handle this. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.