[maemo-developers] MeeGo
From: Christopher Intemann intemann at gmail.comDate: Mon Feb 15 18:55:16 EET 2010
- Previous message: MeeGo, unity or fragmentation?
- Next message: MeeGo
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Feb 15, 2010 at 4:40 PM, Thomas Tanner <tanner at gmx.de> wrote: > The problem is more complex than converting binary .debs to .rpms using > a hack. > 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? > > Since MeeGo is about to become the successor of Maemo, I guess there won't be any need to backport anything. I guess that rpm is just more advanced than deb. Finally, most third party software applicable to date is either binary or rpm, but not deb. It is probably easier to convince developers to port their linux tools to MeeGo if they're already familiar with the package management. Cheers, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.maemo.org/pipermail/maemo-developers/attachments/20100215/e9bdfa32/attachment.htm>
- Previous message: MeeGo, unity or fragmentation?
- Next message: MeeGo
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]