[email protected] wrote: >> if we break ABI between 1.1 and 1.2 we, MeeGo, fscked up and must >> provide a compatibility package. > > libssl is Platform API, so there are no ABI promises made > (sect 3.2.1). (However, the spec used to promise ABI > compatability within a 1.x release.)
if you get an app built and checked as compliant, the binary better stay working, as Arjan says. The spec still contains a bit on this: 1.4.3 Forward and Backward Compatibility Forward compatibility for compliant binaries (ABI) is promised for future versions of MeeGo with the same major version number. The Platform API thing is more a source-level consideration: interfaces may vanish, move into Qt, etc. so you can't /build/ against them in future versions. But the ABI has to stay working over versions. How would we handle devices upgrading to a new release otherwise? "All your apps are broken, check back when vendors have had a chance to build new versions?" We'd look pretty bad in comparison to a couple of well-known systems currently on the market... _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
