Currently, dependencies that do not wish to be installed through rosdep can be specified through the --skip-keys flag. However, at least to understanding, this only excludes packages that are on the top-level of the dependency hierarchy. Take for example the ros_gz_sim package that provides several tools for ROS2-Gazebo integration which depends on the package ros_gz_vendor. If I want to specifically not install all the simulator-specific tools (e.g. to keep my Docker images minimal), I have to create dummy packages to satisfy the requirements (for example using equivs), otherwise rosdep fails.
I know that internally the dependency chain is handled by the system's package manager but is there something that could be added to rosdep directly to support this?
Feel free to close this, if this is out of scope.
Currently, dependencies that do not wish to be installed through rosdep can be specified through the
--skip-keysflag. However, at least to understanding, this only excludes packages that are on the top-level of the dependency hierarchy. Take for example theros_gz_simpackage that provides several tools for ROS2-Gazebo integration which depends on the packageros_gz_vendor. If I want to specifically not install all the simulator-specific tools (e.g. to keep my Docker images minimal), I have to create dummy packages to satisfy the requirements (for example using equivs), otherwise rosdep fails.I know that internally the dependency chain is handled by the system's package manager but is there something that could be added to rosdep directly to support this?
Feel free to close this, if this is out of scope.