Building against Mer in Community OBS

Revision as of 19:55, 17 December 2011

Setting up Build Repositories

To change the build target repositories of your OBS project (part of the project metadata) to build against Mer:

 osc -A https://api.pub.meego.com meta prj home:YOURNAME -e

The XML should look along these lines (make sure you use your own "YOURNAME" value) paying special attention to the <repository> tags which you most likely need to add by yourself:

<project name="home:YOURNAME">
 <title>YOURNAME's Home Project</title>
 <description>Mer is cool</description>
 <person userid="YOURNAME" role="maintainer"/>
 <person userid="YOURNAME" role="bugowner"/>
 <repository name="Mer_Core_armv7hl">
   <path project="Mer:fake:Core:armv7hl" repository="Core_armv7hl"/>
   <arch>armv8el</arch>
 </repository>
 <repository name="Mer_Core_armv7l">
   <path project="Mer:fake:Core:armv7l" repository="Core_armv7l"/>
   <arch>armv7el</arch>
 </repository>
 <repository name="Mer_Core_i586">
   <path project="Mer:fake:Core:i586" repository="Core_i586"/>
   <arch>i586</arch>
 </repository>
</project>

This can also be edited in the web interface, under your project -> Advanced -> Raw config -> Edit

You can also osc branch from these repositories but you need to add repositories manually.

Before trying to issue submit requests to projects that are under automated integration (ex. CE:* projects on community OBS), make sure you have created the correct set of repositories needed.

For each repository in target project, there should be a repository in source project which builds only against the target repository and have at least the same architectures as the target repository they build against.

This can be done easily using the addrepos osc plugin , drop it in your ~/.osc-plugins and run the command :

osc -A https://api.pub.meego.com addrepos MYPROJECT TARGETPROJECT

It will open an editor with the repositories appended to the bottom of your prj meta.