Views
Distribution
(→Overview: added process overview figure: development with OBS) |
(Added figure: development process w/o using OBS) |
||
| Line 4: | Line 4: | ||
=== Overview === | === Overview === | ||
[[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]] | ||
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 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. | ||
Revision as of 05:17, 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
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 overall process of develop with an OBS account is shown in the right figure.
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
- Request a new OBS account
- OBS WebUI: Login and first steps
- OBS WebUI: Link packages and adding a repository
- How to use the command line client for daily operations
- Using OBS chroot for development
- Create image based on new RPM
- Troubleshooting
Development without MeeGo OBS account
- Build and develop packages without OBS
- Example: Recompile kernel
- How to development with multiple packages with dependencies
- Create image based on new RPM
Packaging
Submission to MeeGo
- Checklist for new package submissions
- Developer's checklist for code submissions
- irc / mailing lists / contact
Developer Tools
Image Creation
OBS command line
- Part 1 - initial setup
- Part 2 - checkout & branch
- Part 3 - more commands: localcheckbuild