Plasma active/OBS

Based upon Nemo/OBS

= Getting started with the build system = To get started you will need to activate your MeeGo account for OBS. Upon initial login you will be guided through a mini-process to set up your home repository.

After this it's a good idea to set up  in the Mer Platform SDK with the new account. is a command line front-end for the build service. When issuing  for the first time you will be guided through a mini-process to set up a local default configuration. After the initial set-up completed just fire up your favorite editor and open the file. In the file, change apiurl = https://api.opensuse.org to apiurl = https://api.pub.meego.com

Alternatively you can follow the more detailed instructions here: Osc_Setup Further down in the same file you will find a config section named. Change the section name to, and set the corresponding   and   config options to match your MeeGo account. You can test your  set-up by issuing osc ll which should produce a list of all projects on the MeeGo build server. A more comprehensive "OBS getting started" page is at the MeeGo wiki.

= Nemo Mobile OBS project structure = OBS: https://build.pub.meego.com/, new OBS at https://build.merproject.org/

Maintainer: notmart, #active @ Freenode

In each project there are two sets of repositories. One repository chain that builds against current release of Mer Core and another that builds against the "next" prerelease of Mer Core. These repositories are identified with latest_ and next_, where is the architecture the repository is compiling against.

All the kde plasma active related project are under the kde project, and they follow the following structure:

kde: : :

can be one of the following values: stable, testing or devel


 * each has a complete Plasma Active tree below it and is self-contained (ie no building against projects in a different )
 * compared to Nemo, Plasma Active shouldn't have the hw:* projects, because is reusing those from Nemo, in order to share efforts
 * when a package is QA'ed it moves (how?) to the next phase, in order of devel -> testing -> stable
 * the process from developer point of view starts from 'devel' phase where the changes are submitted, after this it is responsibility of maintainer(s) and QA team(s) to forward the new submission forward and report back on any issues.

The subprojects are described below.

kde: :mw
Compiled against: mer:mds:core:{latest,next}:{arch}/{latest,next}_{arch}

Architectures (schedulers): i586, armv7el, armv7hl (armv8el)

Contains all the software that is needed by KDE software either at build time or run time, but is a 3rd party project, not from the KDE project itself, such as


 * Networkmanager
 * boost
 * gpgme

kde: :ux
Compiled against: kde: :mw

Architectures (schedulers): i586, armv7el, armv7hl (armv8el)

A complete KDE environment compiled with the "mobile" platform profile using Plasma Active as workspace, plus some default touch-optimized applications