DebForMeeGo

(→Why keep deb: Mer was never going to be used anyway! End users comment is entirely subjective not factual. Licencing was never an issue! Multiarch is not packaging format specific!)
(wikify slightly, categorize)
 
(14 intermediate revisions not shown)
Line 1: Line 1:
This page collects all arguments for and against keeping the *.deb package format in MeeGo.
This page collects all arguments for and against keeping the *.deb package format in MeeGo.
-
If you want to support this Idea you can [http://maemo.org/community/brainstorm/view/keep_deb_for_meego/ vote at Brainstorm].
+
If you want to voice your opinion on this Idea, you can [http://maemo.org/community/brainstorm/view/keep_deb_for_meego/ vote at Brainstorm].
== Scope ==
== Scope ==
-
the aim is at least to keep the *.deb package format in the MeeGo distributions aiming at Nokia Phones/ Handhelds.
+
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 arguments here apply to the same extend looking at the whole project.
+
Although using the .deb format throughout the MeeGo project is desirable, not all arguments here apply to the same extent looking at the whole project.
-
== Why keep deb ==
+
== Why Switch MeeGo To DEB (switching Moblin to DEB) ==
* No porting for Maemo packages needed
* No porting for Maemo packages needed
-
* Maemo has the bigger community [CITATION NEEDED]
+
* Maemo has the bigger community [1]
* allows syncing from Debian/ Ubuntu
* 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!
+
* DEB has wider adoptation than RPM [2]
* not to throw away experience gained with maemo which is reflected in the packaging
* 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.
+
* better package management and error correction with DEB tools. (dpkg, apt-get, aptitude, deborphan, debsums, the base DEB framework including pre/post scripts, conflict resolution, dependency management and such)
-
* tools for verifying (e.g. lintian) available
+
-
== Why switch to rpm ==
+
[1] amount of third party applications [http://garage.moblin.org/ here] and [http://maemo.org/downloads/Maemo5/ here]. Also note that a Maemo5 port often involves UI changes, which make it more work.
 +
 
 +
[2] comparing numbers from [http://distrowatch.com/ distrowatch] (Ubuntu/Kubuntu/Xubuntu/etc + Debian against OpenSUSE + Fedora + RedHat + Mandriva)
 +
 
 +
== Why Keep MeeGo As RPM (switching Maemo to RPM) ==
* No porting for Moblin packages needed
* No porting for Moblin packages needed
-
* RPM is LSB-compilant. (standartiztion issue with deb though)
 
* Moblin build infrastructure has more capabilities already in place, such as imaging.
* Moblin build infrastructure has more capabilities already in place, such as imaging.
-
* RPMs can contain license information too
+
 
-
* rpmlint can be used to check for a package quality (like lintian)
+
== Common Advantages of DEB and RPM ==
 +
* Tools for verifying (e.g. lintian and rpmlink) are available and can be used to check for a package quality.
 +
* both RPM and DEB are LSB compilant as ''technically there is no dictated package format, only that [[:wikipedia:Linux_Standard_Base#Choice_of_RPM_package_format|RPM must be supported when installing]]''
== Alternative Solution ==
== 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.
* 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.
* Add the imaging feature to the Deb package.
 +
* The [[Maemo on Debian]] project does not try to convince the official MeeGo to use some upstream but instead works on a distribution which integrates existing Maemo5 and future MeeGo components into a standard Debian distribution.
 +
 +
[[Category:Packaging]]

Latest revision as of 13:39, 6 May 2010

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.

Contents

[edit] 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 desirable, not all arguments here apply to the same extent looking at the whole project.

[edit] Why Switch MeeGo To DEB (switching Moblin to DEB)

  • No porting for Maemo packages needed
  • Maemo has the bigger community [1]
  • allows syncing from Debian/ Ubuntu
  • DEB has wider adoptation than RPM [2]
  • not to throw away experience gained with maemo which is reflected in the packaging
  • better package management and error correction with DEB tools. (dpkg, apt-get, aptitude, deborphan, debsums, the base DEB framework including pre/post scripts, conflict resolution, dependency management and such)

[1] amount of third party applications here and here. Also note that a Maemo5 port often involves UI changes, which make it more work.

[2] comparing numbers from distrowatch (Ubuntu/Kubuntu/Xubuntu/etc + Debian against OpenSUSE + Fedora + RedHat + Mandriva)

[edit] Why Keep MeeGo As RPM (switching Maemo to RPM)

  • No porting for Moblin packages needed
  • Moblin build infrastructure has more capabilities already in place, such as imaging.

[edit] Common Advantages of DEB and RPM

  • Tools for verifying (e.g. lintian and rpmlink) are available and can be used to check for a package quality.
  • both RPM and DEB are LSB compilant as technically there is no dictated package format, only that RPM must be supported when installing

[edit] 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.
  • The Maemo on Debian project does not try to convince the official MeeGo to use some upstream but instead works on a distribution which integrates existing Maemo5 and future MeeGo components into a standard Debian distribution.
Retrieved from "http://wiki.maemo.org/DebForMeeGo"