[email protected] wrote: > I'm a bit confused, so MeeGo compliant OS can only be compliant if it > uses the exact packages from MeeGo? So it is not about the API's but > about the exact packages?
if you look at the rules has having two sides - the requirement on the system to provide an API set, and the requirement on the app to consume (only) that API set, then using exact bits is part of the way consistency is ensured on the system side, while from the app view it's "about the APIs". the full API set is a long way from having behavioral specification and test to the level that you can be fully confident of binary compatibility (some people argue passionately it's something you can never prove, but that's perhaps a different question), so "use the meego source" is the position taken. > Just a theoretical questions, if one would get packages from > fedora/opensuse or any other distribution and create an image > that would pass the MeeGo Compliance tools test set would that > image be compliant? under current rules, no. the tests will look for versions, and if they match, the tools are not any the wiser, but the rule still wants you to use the meego bits. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
