Context Navigation

Some proof-of-concept work has already been done, using the open build service as a target distributed package build system.

The osc works by having a SVN-like workflow locally. Packages tarballs and/or control files (the obs can checkout repositories by itself) are added in a package folder and then checked in to the OSC. On checkin, the osc queues the build.

For now, we focus on ubuntu packages, but we need to keep an eye on the possibility to package for non-deb targets (e.g. RPM) since the obs supports them.

ubuntu:12.04:universe - the ubuntu universe packages that we depend on

gems - the gems manually packaged with gem2deb

rockrobotics - the rock packages

Remaining questions

scheme on integration of the built packages into autoproj installations. There are two ways:

have each binary package should install an osdeps file for themselves, and have a way for autoproj to pick those (e.g. AUTOPROJ_ADDITIONAL_OSDEPS envvar). Issue: they don't get installed automatically by autoproj (i.e. users need to install a package manually)

make the build generator updates osdeps files that then get added to each package set. Users will then have to manually create osdeps overrides if they do not want to use binary packages and we can have flags allowing to disable these osdeps for whole package sets. Additionally, we will probably have to extend the osdeps overrides to be able to catch more than one package.

where to install (/opt/rock to follow the /opt/ros ?)

how to version ? (master/, next/ and date tags for the stable, with a symlink from stable to the "current" date tag)