[MeeGo-dev] RPM vs DEB, the FAQ item?

[Marius Vollmer]

ext Auke Kok <auke-jan.h.kok at intel.com> writes:

> On 02/17/10 10:34, Mika Hanhijärvi wrote:
>
>> I just wonder how are you going to make sure that MeeGo will get eg.
>> security updates fast. It's huge task if you are going to maintain
>> everything from kernel and libraries to full application all by yourself
>> whitout using any upstream distro repository.
>
> Just as we do with moblin right now, there are people paid to do exactly 
> that. [...]

More power to you (us!) then.

I have to say that I, too, find the idea very intriguing to start over
and remove all the historical baggage.  But it does take a lot of
competence, determination, experience, and taste to succeed in the long
run.

If MeeGo has what it takes, I'll be ecstatic.  In fact, I realize I am
producing some stop energy here, which I shouldn't.

My experience with Maemo tells me that, errm, some companies have
trouble producing a viable distribution.  So, from that perspective both
options are great: MeeGo as a derivative with a strong upstream
distribution, or MeeGo as its own strong distribution with alignment to
the rest of the Linux universe.

(But if you are starting over, why use rpm or dpkg?  Aren't there better
package managers out there by now that are more suited for 'embedded'
devices?  For me, the choice of upstream determines the choice of
package format, but if your upstream are source tarballs (or git tags),
you can choose the package format freely, no?)