Include .rosinstall in a version-controlled repository?

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

Julius
955 ●31 ●45 ●56

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?

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

kwc
12244 ●54 ●90 ●132 http://kwc.org/

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

tfoote

58457 ●128 ●550 ●526 http://www.ros.org/

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

Comments

This is what we do. With Github, you don't have to do a full checkout, instead use https://github.com/USERNAME/REPO/raw/BRANCH/file.rosinstall

mjcarroll ( 2011-03-16 04:51:06 -0600 )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 ( 2011-03-16 20:57:13 -0600 )edit

add a comment

Include .rosinstall in a version-controlled repository?

1 Answer

Comments

Question Tools

Stats

Related questions

Include .rosinstall in a version-controlled repository? edit

1 Answer

Comments

Question Tools

Stats

Related questions

Include .rosinstall in a version-controlled repository?