Build Infrastructure/Packagers Developers

Revision as of 15:31, 6 January 2011

These pages are in preparation - contributions welcome.

This track will give you a brief introduction to the features and capabilities of the OBS instance hosted at build.meego.com. Note: You need an account to access build.meego.com. If you have no account, you can still learn how the openSUSE Build Service works at the upstream project's own instance http://build.opensuse.org .

In this track, you'll learn how to use the webinterface, the commandline client and create your first package. The packaging guidelines and more advanced topics are also covered.

How to get started

• You will need a meego.com account
• You will need to contact lbt on the #meego channel (irc.freenode.org) so your account can gain access to the obs system
• go to https://build.pub.meego.com

How to use the webinterface

A series of pages will make you familiar with the basic use of the webinterface. Its divided into several subpages:

• Part 1 - Login and first steps
• Part 2 - Creating a link and adding a repository
• Part 3 - Your first own package
• Part 4 - Subprojects and the project monitor page
• Part 5 - Flags and Attributes

OBS - User Home

• How to use

How to use the commandline client

• Part 1 - initial setup
• Part 2 - checkout of projects, commit
• Part 3 - branch, edit, localbuild, commit, submitreq
• part 4 - more commands: localcheckbuild

MeeGo Packaging guidelines and Howto

• Packaging
• Packaging Guidelines
• Packaging Tutorial

QA Processes around the OBS

The initial focus here is on community applications

• to allow freedom for developers to develop;
• to provide a build service and SDK
• to provide excellent quality assured applications for our "app store";

See the Quality page too.

Multi-Architecture and Multi-Distribution packaging

• architecture macros
• example multi-arch specfile
• distribution macros
• example multi-distribution specfile

Tips & Tricks

• Using OBS chroot for development

Troubleshooting

• repository stacking

The repository dependency resolution is confused when you stack same repositories.

In the following example, Targets:Debian:5.0 repository is used twice: Targets:Debian:5.0 <-> devel:tools:sdk:Debian:5.0:backports <-> Targets:Debian:5.0 <-> Debian_5.0

Make sure to avoid repository stacking and use the appropriate repositories in your project configuration: devel:tools:sdk:Debian:5.0:backports <-> Targets:Debian:5.0 <-> Debian_5.0

IRC / mailinglists / contact

If you need help, you can join #meego or #meego-dev on irc.freenode.net . See also this page about all MeeGo IRC channels.

You can join MeeGo-dev and MeeGo-packaging mailing lists over here.