The policy for adding keys to the rosdep database is that the packages need to be available from the ros repository or from the standard upstream sources.
There are rules for gazebo and gazebo5 because they are available in the upstream. When packages land in upstream we can add them to the rosdep database.
Note that your dependency on gazebo_ros does not actually interact with the rosdep database. The gazebo_ros package is a ROS package in the rosdistro, which is why it ends up with ros-indigo-
in the prefix.
The gazebo team maintains newer versions of gazebo built into debians such as gazebo 5 and 6. Some details are at: http://gazebosim.org/tutorials?tut=ro...
You can also locally modify your rosdep sources to add new rules for gazebo as mentioned on this question by @jose-luis-rivero : http://answers.gazebosim.org/question... however they cannot be added to the default since they rely on the packages.osrfoundation.org repository.
There are
rosdep
keys forgazebo
andgazebo5
, but not forgazebo6
(here). At least those will probably have to be added.Thank you for this information. Can I add the rosdep keys for gazebo6 myself (e. g. with a patch) or is there any official support team I could ask for this feature?
As a workaround I removed the run_depend
gazebo_ros
andgazebo_ros_plugins
from package.xml. Users will have to installros-indigo-gazebo6
andros-indigo-gazebo6-plugins
manually to be able to run the launch files.