Rosanswers logo

We are getting close to release our department ROS repository. We changed the SVN layout so now a trunk/ tags/ and branches/ is available on each stack. The install/update process is handle via rosinstall tool.

Questions are:

  1. We need to provide to the ROS indexer a "whole repository" .rosinstall file, don't we?
  2. Main repository wiki page should be documented before or after asking for inclusion? In the same line, is preferred to create wiki pages for each stack/pkg before or the indexer will create the page for us?
  3. At this moment we haven't got any of our stacks released (using the ROS release tools). is it mandatory, recommended or not related at all before asking for inclusion in the list of repositories?


Originally posted by jrivero on ROS Answers with karma: 138 on 2011-10-31

Post score: 6


1 Answer 1


Rosanswers logo

Here is a good overview of creating your own ROS repository.

  1. At a minimum, send a message to the ros-users mailing list containing the repository address.

Since git and hg repositories generally require separate source URLs for each stack, you may also wish to provide a .rosinstall file, allowing fine-grained control over your part of the index. (For svn repositories, that is often not needed.)

  1. Wiki pages are not created automatically. You are free to create them before or after announcing the new repository.

Please do create them, using the appropriate wiki templates. Some fields will not appear until the indexer finds your code. That's OK.

Personally, I like to create package and stack pages before they appear in the repository. Then, I can easily tell when the indexer has visited them.

  1. Binary ROS releases are not required, but I would recommend them. A good general open source practice is to "release early and often".

Originally posted by joq with karma: 25443 on 2011-10-31

This answer was ACCEPTED on the original site

Post score: 5

Original comments

Comment by joq on 2011-11-01:
Thanks, Ken. I added your comments to the text above for improved readability.

Comment by kwc on 2011-10-31:
@joq, it would also be nice to include this link: http://www.ros.org/wiki/Get%20Involved#Create_Your_Own_.2A-ros-pkg_Repository

Comment by kwc on 2011-10-31:
Correct, thanks for answering. I'll add for #1, rosinstall files are an option we've added for git/hg repositories, mainly because a single institution ends up having an increasing number of repositories over time, and this gives them control over their part of the index.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.