DebForMeeGo

This page collects all arguments for and against keeping the *.deb package format in MeeGo.

If you want to voice your opinion on this Idea, you can vote at Brainstorm.

Scope

The aim is at least to keep the *.deb package format in the MeeGo distributions aiming at Nokia Phones/ Handhelds. Although using the .deb format throughout the MeeGo project is desireable, not all arguments here apply to the same extent looking at the whole project.

Why keep deb

• No porting for Maemo packages needed
• Maemo has the bigger community [CITATION NEEDED]
• allows syncing from Debian/ Ubuntu
  • Moblin promotes pushing back to upstream - Debian/Ubuntu rarely do! There is no need to be "synced" when you work with upstream. This "pro" deb point is actually a minus!
• not to throw away experience gained with maemo which is reflected in the packaging
  • These changes should have been pushed back upstream. Why is Maemo the only benefactor? The larger community should benefit from Maemo experience and then the package format wouldn't matter.
• tools for verifying (e.g. lintian) available

Why switch to rpm

• No porting for Moblin packages needed
• RPM is LSB-compilant.
  • So is deb.
• Moblin build infrastructure has more capabilities already in place, such as imaging.
• rpmlint can be used to check for a package quality (like lintian)

Alternative Solution

• Keep a Debian base system, and provide third-party applications in an LSB package formet (which is RPM inside). LSB-compliant RPM should install flawlessly, and that way the frontier between system packages (DEB) and third-party applications (RPM) is well defined.
• Add the imaging feature to the Deb package.