rosbuild migration - mixing workspaces?

edit

It technically works to build both wet and dry packages from a single folder. The main drawback is that it gets more difficult to keep track what is actually being build since it is not obvious anymore what kind of package a subfolder represents.

catkin_make will only consider folders containing a package.xml file. rosmake will only consider folders containing a manifest.xml file (after adding src to the ROS_PACKAGE_PATH).

And alternative way how to deal with this could be:

• you check out all repos to one location, e.g. "repos"
• you create a catkin workspace and add symlinks one by one to repos or packages under "repos" as soon as you migrate them
• you create a rosbuild workspace and symlink all repos/packages "under" as long as thy are not migrated yes This approach allows you to still manage your repos with one tool but maintain a clean separation of your wet and dry workspaces.

Another way (if e.g. multiple people should share the same setup) would be to modify the rosinstall file in a way that all wet and dry repos are checked out to a different subfolder. That way you can easily share the rosinstall file with other people and they will immediately get the same splitting. (May be https://github.com/dirk-thomas/vcstool/ can be helpful to manage your repositories.)