Ask Your Question

Include .rosinstall in a version-controlled repository?

asked 2011-03-16 02:02:37 -0500

Julius gravatar image

I wonder whether it's useful to include the (in my case manually generated) .rosinstall file into my ROS package's GIT repository. If so, developers can just get the project via GIT and then call rosinstall and source one of the shell scripts in order to compile my project without hassle... Is there any drawback which I might have overlooked?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2011-03-16 03:59:10 -0500

kwc gravatar image

updated 2011-03-16 10:47:33 -0500

tfoote gravatar image

Instead of including the .rosinstall file, it is a much better practice to include the original rosinstall file (no dot prefix). The .rosinstall file encodes information about a specific installation on a specific machine. The original rosinstall file can be safely used to generate any number of installations on multiple machines.

Most VCSs allow you to pull individual files by url.

Then you can write your install instructions like this:

rosinstall ~/my_project /opt/ros/diamondback 'http://my_vcs_server/path_to_file.rosinstall'
edit flag offensive delete link more


This is what we do. With Github, you don't have to do a full checkout, instead use
mjcarroll gravatar image mjcarroll  ( 2011-03-16 04:51:06 -0500 )edit
Thanks, I've implemented this solution. My rosinstall file now does not only include dependencies but also refers to the GIT repository of my own project. I like installation instructions that can be written in one single command-line.
Julius gravatar image Julius  ( 2011-03-16 20:57:13 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2011-03-16 02:02:37 -0500

Seen: 307 times

Last updated: Mar 16 '11