Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

rename 'ros2' command to 'ros'

See original GitHub issue

Feature request

Consider dropping the 2 from ROS command-line executables and rename the ros2 to simply ros for a simpler CLI syntax.

Feature description

The ROS2 command-line tool unnecessarily carries the version number 2. The version number can be dropped as there are no other conflicting ros executables in ROS1.

E.g.: ros2 topic list ⇨ ros topic list ros2 run ⇨ ros run

Implementation considerations

An implementation only needs to consider renaming all references to ros2 scripts. The most amount of work has to be done for updating the documentation about the ROS2 CLI.

Issue Analytics

State:
Created 3 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

clalancettecommented, Aug 4, 2020

Can you explain more what the perceived benefits of a rename are? To me, this seems like it would result in a lot of work, possible confusion with the ROS 1 command-line tools (which are still supported), and a long period of transition. So there would need to be a really strong benefit to convince me.

0reactions

ivanpaunocommented, Aug 27, 2020

It has been discussed in today’s triage meeting, as previously commente, renaming ros2 command as ros would case confusion in all platforms where ros2 coexists with ros.

In a future release where ros2 is the only ros version in the platform, this decision can be reconsidered.