I personally likes to have huge repository with many packages, which makes easy maintenance and also prevent inactive repository from out of my view, however, if you have huge repository, there are potential draw backs on
- longer build time slow down release cycle : Please split out stable packages into separate release units · Issue #919 · jsk-ros-pkg/jsk_common · GitHub
- ros build firm has 120 min limit Jenkins job on `64.91.234.231_sync` does not finish in 120 minutes · Issue #220 · ros-infrastructure/buildfarm · GitHub (this happens if you have large package, not repository)
- travis has 50 min, if you use huge repository, you may need some caching Update .travis for enabling ccache by garaemon · Pull Request #1373 · jsk-ros-pkg/jsk_recognition · GitHub, Update .travis for apt-cacher-ng by garaemon · Pull Request #1394 · jsk-ros-pkg/jsk_recognition · GitHub, [jsk_pcl_ros] Cache test_data to ROS home by wkentaro · Pull Request #1424 · jsk-ros-pkg/jsk_recognition · GitHub …