(This page needs re-writing) |
(→Creating Packages for MeeGo) |
||
| Line 8: | Line 8: | ||
* The package format used by MeeGo is [http://en.wikipedia.org/wiki/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 [http://en.wikipedia.org/wiki/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)]]. | ||
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.
Contents |
Evolving packaging guidelines...
The community will host a Packaging School Weekend which will support developers and packagers in learning to use the OBS and in packaging their applications.
We hope to have expert packagers from both deb and rpm (and some of us new to the art)... find out more
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.