ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

Generally speaking, the repositories are broken up in such a way to minimize the dependency tree of each. For instance, ecto_opencv, ecto_pcl, and ecto_ros each have a significant major dependency (opencv, pcl, ros respectively). The idea here is that many people may only want 2d-image functions and will never use ecto_pcl, so there is no sense installing so many packages to make ecto_pcl work (and vice versa if you are using 3d features primarily).

If all of your cells are interrelated and intended to be used together, then I would suggest a single repository for your new cells. Regardless of where you build your cells, at runtime, it won't make much difference other than your import statements to bring those cells into your final pipeline.