Views
Build Infrastructure
(→MeeGo Build Infrastructure) |
(→System Administrators/Distribution Managers/On-site) |
||
| Line 37: | Line 37: | ||
=== [[Build_Infrastructure/Sysadmin_Distro|System Administrators/Distribution Managers/On-site]] === | === [[Build_Infrastructure/Sysadmin_Distro|System Administrators/Distribution Managers/On-site]] === | ||
| - | * How to | + | * How to set up a Build Service locally for testing |
* Advanced setup topics | * Advanced setup topics | ||
* [[Build_Infrastructure/Sysadmin_Distro#Seamless_cross-compilation.2C_cross-toolchain_integration|Seamless cross-compilation, cross-toolchain integration]] | * [[Build_Infrastructure/Sysadmin_Distro#Seamless_cross-compilation.2C_cross-toolchain_integration|Seamless cross-compilation, cross-toolchain integration]] | ||
| Line 45: | Line 45: | ||
[[File:peep_netbook.png|right]] | [[File:peep_netbook.png|right]] | ||
| + | |||
=== [[Build_Infrastructure/Developing_OBS|Developing for the openSUSE Build Service]] === | === [[Build_Infrastructure/Developing_OBS|Developing for the openSUSE Build Service]] === | ||
* Upstream URLs | * Upstream URLs | ||
Revision as of 17:40, 19 August 2010
Contents |
MeeGo Build Infrastructure
The heart of the Build Infrastructure of MeeGo is the upstream project openSUSE Build Service (OBS). It is an automated system used for building software packages, collaboration of developers, release management, maintenance, and much more. Moblin started using OBS in June 2008 and released Moblin 2.0 and Moblin 2.1, as well as other derivative releases. OBS has proven to be a very reliable infrastructure that is quickly evolving. It is rich with features for distribution building and maintenance. The Linux Foundation is dedicated to the further development of OBS and has a team, including two full time OBS maintainers, contributing to its development and its use by MeeGo and the Ecosystem.
MeeGo currently uses version 1.7.x of OBS and will soon switch to version 1.8. To learn more about version 1.8 and the additional features in it, see the upstream project details: roadmap.
Overview - What does it do?
Lets set out some basics about the OBS.
- It's a build system. You put source on it and say "use this repository" and it builds a minimal SDK-like chroot using the deb/rpms it finds in that repository
- It has packages - a package corresponds to a tarball and a spec/dsc
- It has projects - a project is like a directory with packages
- When a package is built it is "published" from the project where it was uploaded into a corresponding repository (which can be used to build other projects)
- The repositories can also be used by devices to download binary packages.
Choose one of the different tracks and guides for:
Packagers/Developers
- How to use the web interface to view, manage and build your packages.
- How to use the command line client for daily operations
- MeeGo Packaging guidelines and howto
- QA Processes around the OBS
- Multi-Architecture and Multi-Distribution packaging
- Tips & Tricks
- Troubleshooting
- irc / mailing lists / contact
Community Build System
- Also see the Packagers/Developer information above
- The community OBS is located in the maemo.org area until HW arrives at OSU
- QA Processes around the Community OBS
- Details and status updates
System Administrators/Distribution Managers/On-site
- How to set up a Build Service locally for testing
- Advanced setup topics
- Seamless cross-compilation, cross-toolchain integration
- Whats the metadata (prjconf/prj), attributes, admin-tools for.
- Troubleshooting
- irc / mailinglists / contact
Developing for the openSUSE Build Service
- Upstream URLs
- irc / mailing lists / contact
- Roadmap
- MeeGo feature wishlist