On Sat, Nov 19, 2011 at 2:54 PM, Lucas De Marchi <lucas.demar...@profusion.mobi> wrote: > On Sat, Nov 19, 2011 at 12:13 PM, Gustavo Sverzut Barbieri > <barbi...@profusion.mobi> wrote: >> On Sat, Nov 19, 2011 at 12:10 PM, Gustavo Sverzut Barbieri >> <barbi...@profusion.mobi> wrote: >>> On Sat, Nov 19, 2011 at 7:27 AM, Carsten Haitzler <ras...@rasterman.com> >>> wrote: >>>> On Sat, 19 Nov 2011 04:12:46 -0500 Mike Blumenkrantz <m...@zentific.com> >>>> 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 > > Are you willing to maintain 10 versions of econnman in the same library?
Of course not, ideally when you add a new version, like 0.8x you remove the previous one, but people can leave it installed. Raster's point is that the libname.so.version is not saying the ABI was changed, and undefined behavior will happen. As changing version is not an option due bureaucracy of autofoo, then we change the libname. >>> 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. > > This is the only sane way!!! The others are broken by design. yes, but until then we have to live with that >> 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) > > Sorry, I'm not interested in doing that. lazy bitch :-) -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
