I too dislike submodules, and although they would only be necessary for travis if they are there by default it can be confusing/disruptive for developers. If it's only necessary for travis it would be simple to package that functionality into a resource that travis would fetch/install during the setup phase, like it does like any other testing/tooling dependencies which are installed via the .travis `install` segment.
---
[Visit Topic](
https://discourse.ros.org/t/building-ros-on-mac-in-ci/4071/16) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)