[meego-packaging] MeeGo and compatibility with other distros

[Jeremiah Foster]

On Jul 8, 2010, at 12:29, Anas Nashif wrote:

>> 
>> If MeeGo is not following the rpm packaging spec, then they are creating a derivative distro and not being 'close to upstream' as they contend. I think this should get clarified and if sending this to the meego-dev list is the way to do it then yes, fire it off. :)
>> 
> 
> Where exactly we are not following the specs?

The rpm specification. http://en.wikipedia.org/wiki/RPM_Package_Manager

> What is upstream? 

The rpm specification itself[0] in this instance.

> Let not confuse spec with packaging conventions, if we are not following the spec then we would not be able to produce any RPMS. 

No confusion here. If your definition of compliance is that the rpm builds on your build system and it installs on your OS, then sure, you are compliant. The point of rpm though is that you build it once, on any service, and installs anywhere. Otherwise why use it at all? 

If the Linux Standards Base, hosted by the Linux Foundation, which ostensibly hosts MeeGo, is not followed by MeeGo, how can you say it is compliant with upstream?

Jeremiah

0. http://ldn.linuxfoundation.org/lsb/rpm-examples-lsb-31