(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 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, | + | 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, and submit your changes back into MeeGo through the [http://lists.meego.com/mailman/listinfo mailing list]. |
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 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. | ||
| Line 31: | Line 31: | ||
* [[Release_Engineering/Submission_Checklist|Developer's checklist for code submissions]] | * [[Release_Engineering/Submission_Checklist|Developer's checklist for code submissions]] | ||
* [[Build_Infrastructure/Packagers_Developers#IRC_.2F_mailinglists_.2F_contact|irc / mailing lists / contact]] | * [[Build_Infrastructure/Packagers_Developers#IRC_.2F_mailinglists_.2F_contact|irc / mailing lists / contact]] | ||
| + | |||
| + | == Software Repo == | ||
| + | * [[Create and update repos]] | ||
| + | * [[Distribution/Package_Management|Package Management]] | ||
== Developer Tools == | == Developer Tools == | ||
| Line 45: | Line 49: | ||
=== Spec tool === | === Spec tool === | ||
* [[Spectacle|Spectacle]] | * [[Spectacle|Spectacle]] | ||
| - | |||
| - | |||
| - | |||
| - | |||
== Distribution Infrastructure == | == Distribution Infrastructure == | ||
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 |
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, and submit your changes back into MeeGo through the mailing list.
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.