Meego Wiki
From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Debian was not Maemo upstream. corrections about release cycle)
 
(21 intermediate revisions not shown)
Line 1: Line 1:
-
= Creating Packages for MeeGo =
+
This page needs re-writing
-
The build infrastructure is not announced yet, so information here is speculative.
+
It should outline MeeGo policy in the areas of packaging and should link to support pages covering reference and tutorial material.
 +
Don't forget that readers will come from other rpm distros and from deb distros too.
-
What is known:
+
== Creating Packages for MeeGo ==
-
*The package format used by MeeGo is RPM.
+
* The package format used by MeeGo is [[:wikipedia:RPM Package Manager|RPM]]. If you are a packager and used to DEB packages, see [[Packaging/Deb conversion example| conversion example]].
 +
* MeeGo build tools and Infrastructure derive from Moblin.
 +
* MeeGo uses [[Build_System| OpenSUSE Build Services (OBS)]]; see [[Build Infrastructure]] for details.
-
* MeeGo build tools and Infrastructure will probably derive from Moblin's (see [http://moblin.org/documentation/moblin-distro-developers-guide/moblin-infrastructure] and [http://moblin.org/documentation/moblin-distro-developers-guide/build-system]) with hopefully better support for ARM targets.
+
== Packaging Guidelines ==
-
* MeeGo will use [http://en.opensuse.org/Build_Service openSUSE Build Services (OBS)].
+
Evolving [[Packaging/Guidelines|packaging guidelines]]...
-
= Upstream =
+
== Upstream ==
-
As Maemo has had an old version of Debian as an upstream distribution, there have been lots of questions on what will be MeeGo's upstream, and why Maemo's relationship with Debian will be dropped. The answer is that MeeGo is an independent distribution : the only upstream is the projects included into MeeGo such as : kernel.org, X.org, Qt, etc. MeeGo policy is to push all bug fixes to upstream projects.
+
MeeGo is an independent distribution : the only upstream is the projects included into MeeGo such as: kernel.org, X.org, Qt, etc. MeeGo policy is to push all bug fixes to upstream projects.
-
Why not be Debian-based ? Having an upstream distribution has advantages and disadvantages.
+
Why not be <your-favourite-distro>-based? Having an upstream distribution has advantages and disadvantages:
-
Advantages : you benefit from all the packaging, QA and maintenance done in the upstream distribution, thus there is a large selection of available ported software.
+
* Advantages: you benefit from all the packaging, QA and maintenance done in the upstream distribution, thus there is a large selection of available ported software.
-
Disadvantages : you have to align your build infrastructure with your upstream. You are dependent on the release cycle and architecture choices of upstream.
+
* Disadvantages: you have to align your build infrastructure with your upstream. You are dependent on the release cycle and architecture choices of upstream.
-
The choice is to have no upstream for MeeGo. It makes it easier to tailor MeeGo for its target devices, which is quite specific compared to Debian's. Maybe the Debian rhythm of updates would also be inadequate for MeeGo (smartphone OSs are currently evolving at a very rapid pace, but there is more up-to-date Ubuntu and Debian is working on more frequent updates). The Moblin build tools would also not have been compatible with Debian as upstream (this is mostly nonsense, see Mer and OBS). Nonetheless MeeGo will be Linux Standard Base (LSB) compliant and its specific components will probably be available in Debian at some point.
+
MeeGo is tailored for its target devices, which are quite specific.
-
= RPM vs DEB =
+
MeeGo will be Linux Standard Base (LSB) compliant.
-
RPM and DEB in themselves are package formats with roughly equivalent features. So the question to use one or the other is more related to the build tools you decide to use. The choice for MeeGo is to use Moblin Tools and openSUSE Build Services (OBS). The RPM choice is mainly a consequence of this (this is again nonsense, see Mer).
+
[[Category:Packaging]]
-
 
+
-
= Some link =
+
-
*[http://lists.meego.com/pipermail/meego-dev MeeGo-dev mailing list]
+
-
*[http://www.allmeegodevices.com/2010/02/17/meego-a-whole-new-linux-ballgame/ A nice article about why no upsteam]
+

Latest revision as of 15:10, 18 April 2011

This page needs re-writing

It should outline MeeGo policy in the areas of packaging and should link to support pages covering reference and tutorial material. Don't forget that readers will come from other rpm distros and from deb distros too.

Creating Packages for MeeGo

Packaging Guidelines

Evolving packaging guidelines...

Upstream

MeeGo is an independent distribution : the only upstream is the projects included into MeeGo such as: kernel.org, X.org, Qt, etc. MeeGo policy is to push all bug fixes to upstream projects.

Why not be <your-favourite-distro>-based? Having an upstream distribution has advantages and disadvantages:

  • Advantages: you benefit from all the packaging, QA and maintenance done in the upstream distribution, thus there is a large selection of available ported software.
  • Disadvantages: you have to align your build infrastructure with your upstream. You are dependent on the release cycle and architecture choices of upstream.

MeeGo is tailored for its target devices, which are quite specific.

MeeGo will be Linux Standard Base (LSB) compliant.

Retrieved from "http://wiki.meego.com/Packaging"
Personal tools