School Network/Open Build Service

Summary
This patched Sugar Labs instance of the Open Build Service (OBS) has the following intentions:


 * Unattended building of software hosted on Sugar Network for all supported platforms.


 * Be a convenient instrument to create 3rd party repositories with native packages for all supported GNU/Linux distributions.

Sites

 * obs.sugarlabs.org This is an API site, all OBS clients use it to get access to OBS. There is no need to work with the site directly, although that is possible.


 * packages.sugarlabs.org This is an original OBS Web client. It is intended to be used only by people who need to create native packages, i.e., it is not needed for most Sugar developers assuming that Sugar Network will process building procedures in unattended mode.


 * download.sugarlabs.org After building, binary packages will be acceptable from the Sugar Labs download site.

Usage
See original manuals and materials to learn more about what functionality OBS provides.

On top of original OBS behavior, the Sugar Labs instance brings the following new features and common practices.

Special projects
There is a special project, named base; it contains all GNU/Linux distributions that are supported on OBS. All other projects, that are intended for building packages, need to inherit repositories from this project.

GNU/Linux distribution agnostic packages
Instead of using spec files of packages to be built against for every GNU/Linux distribution, it is possible to use a special spec file that will be used as-is in all platforms that Sugar Labs OBS supports.

To create such distro-agnostic packages,


 * upload a sweets.recipe file in special notation to OBS package;
 * upload .tar.gz sources with filename composed using sweets.recipe fields:

- .tar.gz

After that, OBS will start building submitted package on all attached OBS repositories.

Resolve packages
There is new API command that might be used to resolve package names and package dependencies on a particular OBS platform.

GET /resolve?project=PROJECT&repository=REPOSITORY&arch=ARCH&package=PACKAGE[&withdeps][&exclude=PACKAGE]

Where:


 * PROJECT, REPOSITORY, ARCH and PACKAGE identification of particular OBS package;
 * withdeps include dependencies graph of the PACKAGE;
 * exclude restrict dependency graph from bottom side.

For example,

https://obs.sugarlabs.org/resolve?project=OLPC&repository=11.3.1&arch=i586&package=pygame&withdeps&exclude=sugar

Will output:

           

Resources

 * Open Build Service home page.
 * Open Build Service API specification.
 * Downstream patch sources.