From: Gustavo S. B. <bar...@pr...> - 2011-11-19 14:13:50
|
On Sat, Nov 19, 2011 at 12:10 PM, Gustavo Sverzut Barbieri <bar...@pr...> wrote: > On Sat, Nov 19, 2011 at 7:27 AM, Carsten Haitzler <ra...@ra...> wrote: >> On Sat, 19 Nov 2011 04:12:46 -0500 Mike Blumenkrantz <mi...@ze...> said: >>> imo we should always attempt to provide backwards compatibility for as long as >>> possible. I recently updated the notification stuff to use the new spec while >>> still checking for old-style messages, and my e17 pulseaudio code supports all >>> versions back to 0.9.16 (I think, maybe even older). >> >> agreed. in fact the situation is much worse. the e connman api and abi have >> been quite badly broken. see my email about it. > > there is no way. > > And IMO we should make it clear src/lib/dbus is 1.x, everything else > depends on the service API. > > I talked to raster at IRC, I'll rename econnman stuff: > > libeconnman0_7x.so > econnman0.7x.pc > econnman0.7x/E_Connman.h > > making it even more clear. Particularly to 0.x services, but for > instance BlueZ is breaking their API for upcoming 5.x release. > > the problem to provide backwards compatibility is when the service is > huge and the features actually went away or changed in a dramatic way. > If it was just a wording problem, then fine, but logic and all > changed. > > Ideally we'd have e_dbus-codegen that generates .c/h and you can just > place them in your code, like people do with Qt and Glib. BTW, due a visit from our dear Samsung people I'm unavailable until Thursday. If someone can do this changes, please!!! (/me looks at demarchi) -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: bar...@gm... Skype: gsbarbieri Mobile: +55 (19) 9225-2202 |