Difference between revisions of "School Network/Open Build Service"

Revision as of 23:53, 19 September 2012

Summary

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

Unattended building of software from Sugar Network on all supported platforms.

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

For detailed information, read the original Open Build System documentation.

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.

The site uses HTTP Basic authentication. To get access, create a Sugar Labs Central Login account.

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. But, until a more appropriate tool is created for Sugar needs, it is the only Web client available to manage already released software (those released by being processed by the sweets command).

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.

Distribution agnostic packages

Instead of using spec files of packages to be built against for every 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:

<implement>-<version>.tar.gz

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

Resolve packages and dependencies

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:11.3.1&repository=Fedora-14&arch=i586&package=pygame&withdeps&exclude=sugar

Will output:

<resolve>
  <binary name="pygame" url="http://mock.laptop.org/cgit/koji.dist-f14-i686/plain/RPMS/pygame-1.9.1-3.fc14.i686.rpm" />
  <binary name="SDL" url="http://mock.laptop.org/cgit/koji.dist-f14-i686-updates-11.3.1/plain/RPMS/SDL-1.2.14-11.fc14.i686.rpm" />
  <binary name="SDL_mixer" url="http://mock.laptop.org/cgit/koji.dist-f14-i686/plain/RPMS/SDL_mixer-1.2.11-4.fc14.i686.rpm" />
  <binary name="SDL_image" url="http://mock.laptop.org/cgit/koji.dist-f14-i686/plain/RPMS/SDL_image-1.2.10-1.fc13.i686.rpm" />
  <binary name="numpy" url="http://mock.laptop.org/cgit/koji.dist-f14-i686/plain/RPMS/numpy-1.4.1-6.fc14.i686.rpm" />
  <binary name="SDL_ttf" url="http://mock.laptop.org/cgit/koji.dist-f14-i686/plain/RPMS/SDL_ttf-2.0.10-1.fc14.i686.rpm" />
  <binary name="portmidi" url="http://mock.laptop.org/cgit/koji.dist-f14-i686-updates-11.3.1/plain/RPMS/portmidi-200-5.fc14.i686.rpm" />
  <binary name="libmikmod" url="http://mock.laptop.org/cgit/koji.dist-f14-i686/plain/RPMS/libmikmod-3.2.0-11.beta2.fc14.i686.rpm" />
  <binary name="libgfortran" url="http://mock.laptop.org/cgit/koji.dist-f14-i686/plain/RPMS/libgfortran-4.5.1-4.fc14.i686.rpm" />
  <binary name="python-nose" url="http://mock.laptop.org/cgit/koji.dist-f14-i686/plain/RPMS/python-nose-0.11.3-5.fc14.noarch.rpm" />
  <binary name="python-setuptools" url="http://mock.laptop.org/cgit/koji.dist-f14-i686/plain/RPMS/python-setuptools-0.6.14-3.fc14.noarch.rpm" />
  <binary name="atlas" url="http://mock.laptop.org/cgit/koji.dist-f14-i686/plain/RPMS/atlas-3.8.3-18.fc14.i686.rpm" />
</resolve>

Note that url attributes might be invalid if corresponding packages were used for building on OBS. So, keep special OBS projects, used only for resolving purposes, like OLPC:11.3.1.

Policy

REDIRECT School Network/Open Build Service/Policy

Resources

Open Build System home page.
Open Build System API specification.
Downstream patch sources.

@@ Line 3: / Line 3: @@
 This [http://git.sugarlabs.org/0sugar/build-service patched] Sugar Labs instance of the [http://openbuildservice.org/ Open Build System] (OBS) has the following intentions:
-* Unattended building of software from [[Sugar Network]] on all [[#Supported_platforms|supported]] platforms.
+* Unattended building of software from [[Sugar Network]] on all [[Harmonic_Distribution/Supported_platforms|supported]] platforms.
-* Be a convenient instrument to create 3rd party repositories with native packages for all [[#Supported_platforms|supported]] GNU/Linux distributions.
+* Be a convenient instrument to create 3rd party repositories with native packages for all [[Harmonic_Distribution/Supported_platforms|supported]] GNU/Linux distributions.
 For detailed information, read the original Open Build System [http://openbuildservice.org/documentation.html documentation].
@@ Line 21: / Line 21: @@
 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. But, until a more appropriate tool is created for Sugar needs, it is the only Web client available to manage already released software (those released by being processed by the [[Platform_Team/Guide/Sweets_Packaging#Releasing|sweets command]]).
-== Content ==
+== Usage ==
-The content on OBS might be of several kinds:
-=== Projects ===
-Projects are directories of Packages and might be of two types:
-* top level, regular projects, like {{Code|base}} or {{Code|sdk}};
-* user's home projects, like {{Code|home:''<user>''}}.
-=== Packages ===
-Packages represent particular software projects and contain all files associated with these projects, e.g., tarballs with sources.
-There are several types of packages supported on OBS:
-* packages that represent sweets,
-* native packages based on sweets,
-* native packages using sweet recipes as spec files,
-* aliases,
-* regular OBS packages.
-See [[#Usage|Usage]] section for more details.
-=== Repositories ===
-Every project has repositories to build its packages against. Repositories might be of two types:
-* inherited from another project;
-* initial repositories, aka, downloaded-on-demand, that are associated with a particular GNU/Linux distribution release;
-Note: The {{Code|sweets.sugarlabs.org}} repository should be present if Packages need to be distributed via Zero Install.
-Every repository has supported architectures, e.g., {{Code|i586}} or {{Code|x86_64}}. There is also the special architecture, {{Code|0install}}, only for {{Code|sweets.sugarlabs.org}}.
-== Supported platforms ==
+See original [http://openbuildservice.org/help/manuals/ manuals] and [http://openbuildservice.org/help/materials/ materials] to learn more about what functionality OBS provides.
-There is a special project, named [https://packages.sugarlabs.org/project/repositories?project=base base]; it contains all GNU/Linux distributions that are supported on OBS. All other projects need to inherit repositories from this project.
+On top of original OBS behavior, the Sugar Labs instance brings the following new features and common practices.
-== Usage ==
+== Special projects ==
-On top of original OBS behavior, the Sugar Labs patch brings the following new features.
+There is a special project, named [https://packages.sugarlabs.org/project/repositories?project=base 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.
 === Distribution agnostic packages ===