Same rosdep key for a system dependency and a ROS package
Will it create conflicts if I try to release a ROS package which has the same name as a rosdep key for an existing Debian package? So, basically, if I'm not mistaken it will be a new entry in the distribution file:
https://github.com/ros/rosdistro/blob...
with the same name as an existing entry in the rosdep keys list:
https://github.com/ros/rosdistro/blob...
So, assuming that it is possible, what will happen when somebody will depend on that package in their package.xml: will rosdep get confused or will it choose one of the two alternatives and if so which one will it be (the ROS package or the Debian package or the behaviour is non-deterministic)?
Thanks.