Isn't that an example of the developer mess that's rapidly approaching? If you're saying attila77's list wasn't accurate (and it correlates with my understanding), we've got a problem if one of the leading Qt developers and experts on maemo.org is confused.

Which is the official API? Is it MeeGo Touch or Qt? If you want to build a "MeeGo" application or a cross-platform (MeeGo, Maemo 5, MeeGo-Harmattan, Symbian) application it's the latter. If you want to build a "MeeGo Handset" application, is MeeGo Touch the official API?

There's overlap here with http://forum.meego.com/showthread.php?t=524&page=2 - but we, as developers are telling you, we're already confused with the relationship between MeeGo-Harmattan, MeeGo and Maemo. Saying "stick with the official API" doesn't help us, we've been developing applications for 5 years and want to migrate them to new platforms with as little work as possible.

Well, there's been no evidence of handling the production of deb specifics automatically from within the tools which are coming out now; so what's to assume that they'll handle deb *and* RPM packaging details? OBS should help developers at a high-level, but there's all manner of specifics to be hammered out (think dependencies which might be named differently on different platforms).