We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently Universal_Robots_ROS2_Driver.humble.repos has a flat structure. It might be better to have a structure similar to ros2.repos
src$ tree -L 2 . ├── ros-controls │ ├── control_msgs │ ├── control_toolbox │ ├── kinematics_interface │ ├── realtime_tools │ ├── ros2_control │ └── ros2_controllers ├── ros-industrial │ └── ur_msgs └── UniversalRobots ├── Universal_Robots_Client_Library └── Universal_Robots_ROS2_Description
The text was updated successfully, but these errors were encountered:
The repos file is mainly meant for CI testing, so I don't necessarily see the benefits of structuring this.
Sorry, something went wrong.
np, I just read in the installation it can be used for the source build, and I found it inconvenient to use in this form.
No branches or pull requests
Currently Universal_Robots_ROS2_Driver.humble.repos has a flat structure. It might be better to have a structure similar to ros2.repos
src$ tree -L 2 . ├── ros-controls │ ├── control_msgs │ ├── control_toolbox │ ├── kinematics_interface │ ├── realtime_tools │ ├── ros2_control │ └── ros2_controllers ├── ros-industrial │ └── ur_msgs └── UniversalRobots ├── Universal_Robots_Client_Library └── Universal_Robots_ROS2_Description
The text was updated successfully, but these errors were encountered: