On Fri, Dec 17, 2010 at 04:02:31PM +0100, [email protected] wrote: > 1. list the symbols exported by your library (current package) > 2. list the symbols exported by your library (new package) > 3. compare the symbols and check for ABI breakage
None of these help in the cases where there is no library between the applications and the services they depend on, such as DBus services. For example, oFono and connman. Until recently, there were no supported or maintained Qt APIs for these, so most apps that use them, do so through straight QDBus interfaces, which, as you know, do not have headers or symbols available in the build environment that are checkable like these. It's even more complicated since the services are not build requirements at all, just runtime install requirements (and really, as Jussi pointed out, not even a true requirement, as their abscence can usually be handled gracefully). With the recent introduction of libofono-qt, this could be improved, in that now this problem could be minimized to just libofono-qt and ofono (assuming all apps move to using it). But libofono-qt will still need to be tracking to specific versions of ofono unless someone owns verifying all functionality (which, btw, is impossible, due to differences in carrier services, networks, etc) or at least, looking for both name and behavior differences in the ofono DBus APIs. This problem has bit us many many times, and as of yet, I've seen only so-so ideas, and no true "ownership" from QA or package maintainers on coming up with a real solution (if one exists). My 0.02 Shane... > It could be automated and OBS could provide it (see Anas's postchecks > repository). > > Cheers, > > Fathi > ________________________________________ > From: [email protected] [[email protected]] > On Behalf Of ext Alberto Mardegan [[email protected]] > Sent: Friday, December 17, 2010 4:22 PM > To: [email protected] > Subject: Re: [meego-packaging] Send notifications if ABI/API changes > > On 12/17/2010 03:54 PM, Zhu, Peter J wrote: > > So, once a package update/upgrade involves a ABI changes, before submitting > > to T:T, please send an notification to meego-dev and meego-packaging and > > let release engineers know with detailed information of > > * what has changed, > > * what are required to do in upper stack to work with the ABI changes > > Is there some tool you'd recommend to check for ABI incompatibilities? > AFAIK, OBS doesn't provide such functionality. > > Ciao, > Alberto > > -- > http://blog.mardy.it <-- geek in un lingua international! > _______________________________________________ > MeeGo-packaging mailing list > [email protected] > http://lists.meego.com/listinfo/meego-packaging > _______________________________________________ > MeeGo-packaging mailing list > [email protected] > http://lists.meego.com/listinfo/meego-packaging -- Shane... _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
