Views
Build Infrastructure
(→MeeGo Build Infrastructure) |
(→MeeGo Build System) |
||
| Line 29: | Line 29: | ||
Having these areas allow us to support: | Having these areas allow us to support: | ||
| - | |||
* Managing packages as part of their acceptance into MeeGo core | * Managing packages as part of their acceptance into MeeGo core | ||
* Deprecating packages from MeeGo core | * Deprecating packages from MeeGo core | ||
Revision as of 22:52, 14 April 2011
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 OBS version 2.1.1. To learn more about version 2.1 and the additional features in it, see the upstream project details: roadmap.
There are 3 OBS instances that are relevant to MeeGo
- MeeGo core: essentially, if you're a core package maintainer/developer you get an account here
- MeeGo build system: for anyone to build applications or libraries against MeeGo - anyone with a meego.com account can use this
- openSuse: this is not for building *against* MeeGo... but we need to support MeeGo tools on many platforms and some of those get built on the openSuse OBS
Overview - What does it do?
Let's 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.
MeeGo Build System
The MeeGo build system is part of meego.com infrastructure and supports several important kinds of development:
- Applications to run on MeeGo
- Surrounds: the MeeGo contribution and sharing area. (This is the repository with dependencies to support Applications to run on MeeGo, think debian contrib, or ubuntu universe)
- Team Repositories
- Personal Repositories
Having these areas allow us to support:
- Managing packages as part of their acceptance into MeeGo core
- Deprecating packages from MeeGo core
- A high quality distribution built around MeeGo core
Choose one of the different tracks and guides for:
Packagers/Developers
- How to get started.
- 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
- Verifying Your Package Changes Locally and Online
- Troubleshooting
- irc / mailing lists / contact
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