Meego Wiki
Views

Distribution

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Added figure: development process w/o using OBS)
(Clean up the overview paragraph.)
Line 5: Line 5:
[[File:Distribution-process-overview-with-obs.png|thumb|250px|right|The development process when using OBS]]
[[File:Distribution-process-overview-with-obs.png|thumb|250px|right|The development process when using OBS]]
[[File:Distribution-process-without-obs.png|thumb|250px|right|The development process w/o using OBS]]
[[File:Distribution-process-without-obs.png|thumb|250px|right|The development process w/o using OBS]]
-
Like other Linux distros, MeeGo is a package-based system, and it is using [http://www.rpm.org/max-rpm/index.html RPM] package end. The RPM packages are managed in [http://wiki.meego.com/Zypper Zypper] repos. The MeeGo development is done by using the upstream project [http://wiki.opensuse.org/Portal:Build_Service Open Build Service (OBS)]. If you are a serious and frequent MeeGo contributor, you need an OBS account to commit your changes back to MeeGo. Other casual contributors can work without using OBS, but you need a MeeGo development team member to help review and commit your changes into MeeGo.
+
Like other Linux distros, MeeGo is a package-based system, and it is using [http://www.rpm.org/max-rpm/index.html RPM] package end. The RPM packages are managed in [http://wiki.meego.com/Zypper Zypper] repos. The MeeGo development is using [http://wiki.opensuse.org/Portal:Build_Service Open Build Service (OBS)] to manage and build packages. If you are a serious and frequent MeeGo contributor, you need an OBS account to commit your changes back to MeeGo. Casual contributors can work without using OBS, but you need a MeeGo development team member to help review and commit your changes back into MeeGo.
-
The overall process of develop with an OBS account is shown in the right figure.
+
The overall processes of development with and without an OBS account are shown in the right figures. Detail description of the processes can be found below.
-
 
+
-
The process of develop without using OBS:
+
-
Download MeeGo from a repo, build a chroot env, get the source of a package, make changes, build and test the new package, how to debug the local build, find a MeeGo team member to sponsor your changes and submit them back.
+
=== Development with MeeGo OBS account ===  
=== Development with MeeGo OBS account ===  

Revision as of 05:21, 7 July 2011

This page describes basic information you needed if you want to contribute to MeeGo. Target audience is community member who wish to involve in MeeGo development.

Contents

Package Management and Development

Overview

The development process when using OBS
The development process w/o using OBS

Like other Linux distros, MeeGo is a package-based system, and it is using RPM package end. The RPM packages are managed in Zypper repos. The MeeGo development is using Open Build Service (OBS) to manage and build packages. If you are a serious and frequent MeeGo contributor, you need an OBS account to commit your changes back to MeeGo. Casual contributors can work without using OBS, but you need a MeeGo development team member to help review and commit your changes back into MeeGo.

The overall processes of development with and without an OBS account are shown in the right figures. Detail description of the processes can be found below.

Development with MeeGo OBS account

Development without MeeGo OBS account

Packaging

Submission to MeeGo

Developer Tools

Image Creation

OBS command line

Spec tool

Software Repo

Distribution Infrastructure

Links

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