(→Distribution Infrastructure) |
(→Overview) |
||
| Line 10: | Line 10: | ||
The process of develop without using OBS: | 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. | 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 === | ||
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 the upstream project 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.
The process of develop with an OBS account: Branch, Check-out, Make changes, Deployment the new package and test, Make a new image (optional), Submit your changes.
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.