[Rock-dev] Heavy changes in rock's autoproj configuration

[Ruun]

Hi, i got some problems which is relating to this changes.

Is the current version still compatible with the old convention in 
autoproj?  (Or do i need to add your proposed fixes for all package sets 
and the manifest for resolving my current problem).

If i try to update, i got a failure with the following message:
$ updating autoproj main configuration
$
$ in 
/home/chris/repos/rimres/autoproj/remotes/rock.toolchain/source.yml: the 
source specification {:gitorious=>"orocos-toolchain/autoproj"} misses 
either the VCS type or an URL

My Autoproj-version is v1.7.12.

Chris



On 17.08.2011 09:59, Sylvain Joyeux wrote:
> Everything seems to be fine
> For maintainers of autoproj configuration and package sets, you need to
> remove the "branch: $ROCK_FLAVOR" stanzas from your autoproj/manifest
> (if you had it) when importing rock (and, internally at DFKI, rock-dfki)
> package sets. Idem for import configurations in the package set's
> source.yml files.
>
> Additionally, the shortcut
>
>      gitorious:<project_name>/<repository_name>
>
> can now be used instead of having to write the complete importer
> definition. Internally at DFKI,
>
>      spacegit:<project_name>/<repository_name>
>
> works as well. For instance:
>
>      gitorious: rock/package_set
>
> Sylvain
> _______________________________________________
> Rock-dev mailing list
> Rock-dev at dfki.de
> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev