Hi Jeremiah, Jeremiah Foster wrote: > On Apr 26, 2010, at 10:10 AM, Dave Neary wrote: >> As I understand it, to call yourself MeeGo, you have to have all the >> core components of the platform & applications as defined by the MeeGo >> project, and must use them all. RPM is part of the core platform definition. >> >> Nothing is stopping someone from re-packaging all the MeeGo components >> using deb, but you wouldn't be able to call it MeeGo. > > Sounds like you describing a 'compliance' path for MeeGo. Do you know of an > official path to MeeGo compliance Dave?
As you know, the official compliance suite is not available yet - the MeeGo legal page says it'll be published during the MeeGo 1.0 release cycle. I am going on what was said by Arjan during his presentation at the Collaboration Summit. It is not sufficient, according to Arjan, to simply ensure that the core components ship on a device and use other components, you must use the specified libraries, interfaces and data stores to ensure that applications can integrate well together. Cheers, Dave. -- maemo.org docsmaster Email: [email protected] Jabber: [email protected] _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
