Hi Steven,
The code that generates the megamanifest.xml is here:
https://code.ros.org/svn/ros/stacks/rosorg/trunk/rosbrowse
I imagine that a parallel version with stacks needs to be created,
which should mostly be string substitution (use the roslib.stacks api
instead). It might be possible to generate just one file for both,
but we'd have to test backwards-compatibility with other scripts that
read the same file.
Then it should just be a matter of modifying 'roslocate' to read the new data.
There is additional work to add it to our automated builds so that the
file gets updated on our server. I'm happy to help integrate this if
you submit a patch.
- Ken
On Fri, Jun 18, 2010 at 2:00 AM, steven bellens <
bellenssteven@gmail.com> wrote:
> Hi,
> I'm trying to set-up an automated build of several ros stacks/packages. In
> order to install all dependencies (packages _and_ stacks) support for the
> roslocate command to locate stacks would be very useful. This probably means
> generating a megamanifest.xml file for stacks similar to the one already
> available for packages. Is it possible to add this functionality? Or give me
> instructions on how to do so?
> best regards,
> Steven Bellens
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
(text/plain)