[maemo-developers] MeeGo

[From: Luca De Cicco]

I would stay away of packaging holy wars (packaging is boooring) :).
It is true that packaging has some technical implications, however
I would focus more on the scenario we are going to experience.

How  and who will manage the community efforts?
Is MeeGo going to be deployed on real commercial products (nokia phones,
tv sets)?

Generally, I'm a bit cautious when new mobile/embedded OS hit the news.
All of them promise heaven, but then very few are deployed in real
products (that is
Symbian, windows CE).

just my two cents,
Luca

On Mon, Feb 15, 2010 at 5:21 PM, Thomas Tanner <tanner at gmx.de> wrote:
> On 15.02.10 16:47, Jeremiah Foster wrote:
>>> The problem is more complex than converting binary .debs to .rpms
>>> using a hack.
>> alien is not a hack.
>
> the hack referes to a process ignoring the issues listed below. No
> automated process can take into account all the distribution and program
> specific quirks.
>
>>> The dependencies, the build script and Debian (ucf, debconf) or
>>> Maemo (maemo-optify) specific aspects of the sources would need to
>>> be adapted as well. Backporting to Maemo5 would also be more
>>> difficult.
>>
>>> Who benefits more from the merger, Moblin or Maemo?
>> Both benefit if we get the kind of scale that is imagined.
>
> I'm not critising the merger itself, but how and what is merged
> and whether that are top-down decisions or whether the community is
> involved.
>
> AFAIK there a hardly any Moblin specific third-party apps.
> It could be much less effort to integrate the Moblin components
> in a Debian based system than converting all Maemo apps to Moblin/RPM.
>
> --
> Thomas Tanner ------
> email: tanner at gmx.de
> GnuPG: 1024/5924D4DD
> _______________________________________________
> maemo-developers mailing list
> maemo-developers at maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>