We have had good success adding a single rosinstall file to the indexer, as
Ken suggested earlier. Also, keeping each stack in it's own git repository
saves many of the hassles with submodules.
We keep a rosinstall file in the root of one of our repositories (
https://github.com/Auburn-Automow/au_automow_common/blob/master/au-automow.rosinstall),
and gave Ken the "raw" address (
https://raw.github.com/Auburn-Automow/au_automow_common/master/au-automow.rosinstall
).
That way if you are going to be adding stacks later, you can modify the
rosinstall file yourself, rather than having to announce on ros-users or
bug Ken.
~mc
2012/2/3 Martin Günther <
mguenthe@uos.de>
> On Fri, 3 Feb 2012 17:18:46 +0100
> Thomas Moulard <thomas.moulard@gmail.com> wrote:
> > I suggest adding these packages as submodules of the current stack.
> > In this case, there is no need to register them directly.
>
> Hi Thomas and Fabien,
>
> using Git submodules is fine of course, but just to point out another
> option: you can release each stack as a separate Git repo, then add
> them to a rosinstall file and adding that to the indexer. See this mail
> [1] by Ken Conley to ros-users. This approach makes it possible to
> develop and check out each stack separately while avoiding certain
> problems with Git submodules (such as this one [2]).
>
> [1] https://code.ros.org/lurker/message/20110816.202545.649d3b91.en.html
> [2] https://code.ros.org/lurker/message/20110816.162454.c32a9704.en.html
>
> Cheers,
> Martin
>
> --
> Dipl.-Inf. Martin Günther
> Universität Osnabrück
> Institut für Informatik
> Albrechtstr. 28 (Raum 31/503)
> D-49076 Osnabrück
>
> Fon: 0541 969 2434
> http://www.inf.uos.de/mguenthe/
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
(text/plain)