-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestions: use more specific package names? #28
Comments
I started to have a look at the new packages names and I noticed that the standard convention for the ros2/moveit2 packages is |
Ok for me! However, I would try to avoid names like |
What about |
Ok, it make sense as it clarify that the package contains controllers for
What about |
PR opened here: |
We can discuss on this in person, but I wanted to mark this down somewhere. I may be wrong, but it seems to me the CMake/ROS 2 packages installed by this repo have quite generic names (for example
robot_controller
,robot_moveit
,test_controller
) that may be prone to collisions. Such generic names are fine if they were just folders in a repo (as the name of the repo itself would result in a sort of namespace) but in this case the names are also used to install files in global location.to avoid this problem, could it make sense to prefix all packages with
xcub_moveit2_
? This is a common pattern in ROS repos that contain multiple ROS packages see for example:moveit_
)nav_
)Probably it could make sense to change this before making the repo available in the superbuild (see robotology/robotology-superbuild#1746)?
The text was updated successfully, but these errors were encountered: