AFAIUC currently rqt_dep only shows ROS package (or catkin package to be more precise?). It'd be nice if it shows non ROS packages in addition.
I assume traversing packages is done by rospkg functionality, which uses information in package.xml where non-catkin package dependencies can be listed up. Since rospkg can return non-catkin? package names by e.g. RosPack.get_rosdeps, we should be able to add this functionality.
Note I don't think rospkg can find the dependency of non-catkin packages.
This doesn't have to be done in ROS ecosystem (although so far I haven't found other tools that visualize dependency tree well), but because implementation might not be that hard, I think it's worthwhile feature.
AFAIUC currently
rqt_dep
only shows ROS package (orcatkin
package to be more precise?). It'd be nice if it shows non ROS packages in addition.I assume traversing packages is done by
rospkg
functionality, which uses information in package.xml where non-catkin package dependencies can be listed up. Since rospkg can return non-catkin? package names by e.g.RosPack.get_rosdeps
, we should be able to add this functionality.Note I don't think rospkg can find the dependency of non-catkin packages.
This doesn't have to be done in ROS ecosystem (although so far I haven't found other tools that visualize dependency tree well), but because implementation might not be that hard, I think it's worthwhile feature.