On Fr, 2010-12-17 at 14:22 +0000, Alberto Mardegan wrote: > 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?
Wasn't some Nokia-internal tool mentioned on one of the lists? Okay, mostly some shortcomings were discussed, but it seemed to ways ahead of doing these checks manually. As Shane said, at the end of the day, no such tool will ever be able to replace due diligence by the developers making changes. Shane mentioned D-Bus APIs. The Qt signal and slot names are another recent one. This only shows up only in the strings embedded inside the library. -- 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. _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
