Packaging

Revision as of 08:59, 13 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

• The package format used by MeeGo is RPM. If you are a packager and used to DEB packages, see conversion example.
• MeeGo build tools and Infrastructure derive from Moblin.
• MeeGo uses OpenSUSE Build Services (OBS); see Build Infrastructure for details.

Packaging Guidelines

Evolving packaging guidelines...

Packaging School

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

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.