Description
So ..
having a time machine that can go back to datetimes before Jan 2014 is nice, but also means that we run the risk of packages not being Catkin packages yet, but still using rosbuild.
rosinstall_generator can easily generate .rosinstall files that split out the catkin pkgs from the rosbuild ones, but apart from having two .rosinstall files, we'd also need two workspaces:
- one for the rosbuild packages
- another for the catkin packages
the catkin workspace should then overlay the rosbuild one.
This can get hairy (circular dependencies and all), but catkin cannot build rosbuild packages, and rosmake cannot build catkin pkgs. And catkin workspaces can only extend/overlay rosbuild workspaces, not the other way around.
summarising: as I see it now, the Dockerfile would need to be updated to accept two .rosinstall files. It would be good if we could use default args or optional args though. A lot of bugs won't need it.
Then rosmake would need to be used for one workspace, and catkin for the other.
Dependency resolution should be relatively similar -- if not identical. rosdep was around back then and used in a similar way.