| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
I'm trying to set up a repository which makes it easy for new developers to join the project. To do so I'm considering checking a catkin workspace; doing so without the constituent packages. Are there any known pitfalls to doing this?
Is there a recommended way to create one-step checkout and go setups?
Probably not the best solution.
It might be more productive to discuss the problems with the ROS usability scripts mailing list.
It should be possible to write a script that creates a workspace and populates it from a rosinstall file all in one command with relatively few required parameters. That would be useful to everyone.
I'm also considering the script option, but am wary that any new adjustments to the setup couldn't be done directly and checked in, but rather would need to be done indirectly in the script and then verified in a fresh checkout. I'm curious about the specific reasons it might be a bad idea.
Asked: 2014-03-20 11:04:17 -0500
Seen: 180 times
Last updated: Mar 21 '14
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
What are you actually proposing to check in? My workspace is effectively empty without any packages.
My colleges are versioning complete workspaces. There are a few things to take care of. For example that the .rosinstall includes absolute paths, but they successfully versioned workspaces.
Be sure to not check in any generated files, such as devel or build folders. Can you motivate what exactly you want to do? It seems by providing a .rosinstall new developers can setup their workspace with just 2-3 commands.