(→Overview: Details of overview.) |
(→Overview: Drafted overview paragraph.) |
||
| Line 3: | Line 3: | ||
== Package Management and Development == | == Package Management and Development == | ||
=== Overview === | === Overview === | ||
| - | + | 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 done by using [[Open Build System]] (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. | |
| - | Two flowcharts: one is how to development with OBS, the other is the workflow of how to development without using OBS. | + | TODO: Two flowcharts: one is how to development with OBS, the other is the workflow of how to development without using OBS. |
* MeeGo is using RPM as package end and ZYpper for repo | * MeeGo is using RPM as package end and ZYpper for repo | ||
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 done by using Open Build System (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.
TODO: Two flowcharts: one is how to development with OBS, the other is the workflow of how to development without using OBS.