(wikify section headings) |
Uhofemeier (Talk | contribs) |
||
| (One intermediate revision not shown) | |||
| Line 8: | Line 8: | ||
* 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]]. | * 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 build tools and Infrastructure derive from Moblin. | ||
| - | * MeeGo uses [[Build_System| OpenSUSE Build Services (OBS)]]. | + | * MeeGo uses [[Build_System| OpenSUSE Build Services (OBS)]]; see [[Build Infrastructure]] for details. |
== Packaging Guidelines == | == Packaging Guidelines == | ||
Evolving [[Packaging/Guidelines|packaging guidelines]]... | Evolving [[Packaging/Guidelines|packaging guidelines]]... | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
== Upstream == | == Upstream == | ||
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.
Evolving packaging guidelines...
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:
MeeGo is tailored for its target devices, which are quite specific.
MeeGo will be Linux Standard Base (LSB) compliant.