(→Tips & Tricks) |
(→MeeGo Packaging guidelines and Howto) |
||
| Line 25: | Line 25: | ||
* [[Packaging|Packaging]] | * [[Packaging|Packaging]] | ||
* [[Packaging/Guidelines|Packaging Guidelines]] | * [[Packaging/Guidelines|Packaging Guidelines]] | ||
| + | * [[Packaging/Tutorial|Packaging Tutorial]] | ||
| + | |||
== [[Build_Infrastructure/QA|QA Processes around the OBS]] == | == [[Build_Infrastructure/QA|QA Processes around the OBS]] == | ||
The initial focus here is on community applications | The initial focus here is on community applications | ||
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. A public instance is being setup and will be announced shortly. If you have no account, you can still learn how the openSUSE Build Service works at the upstream projects 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.
Contents |
A series of pages will make you familiar with the basic use of the webinterface. Its divided into several subpages:
The initial focus here is on community applications
See the Quality page too.
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
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.