Dependency on abb_driver about abb HOT 6 CLOSED

This also came up over at abb_experimental: ros-industrial/abb_experimental#129.

And nit-picking, but:

there's no real dependency on it for the actual content of this repository that only has support packages but nothing related to control

is not entirely true.

All support packages come with .launch files which depend on abb_driver.

We can remove it all, but that will require someone to write documentation/tutorials to explain how users are supposed to create .launch files for their robots.

We see the same thing in kuka_experimental: there support packages do not come with any .launch files other than load_...launch and test_...launch, and every so often questions are posted / emailed about how to "control real robots".

from abb.

And another related discussion: ros-industrial/ros_industrial_issues#50 -- with a potential approach to at least notifying users as to why the provided .launch files don't work if they don't install abb_driver (or RViz in that case).

from abb.

I see. The options discussed in the rviz one are interesting. I would have assumed that adding a little comment to the launch file saying <!-- Make sure rviz is installed to use this launch file --> would suffice. I think the same applies here, this doesn't need to be overengineered, a simple note inside these files should be enough. But if you think that's not a viable option, feel free to close this.

from abb.

I'll release abb_driver for Noetic.

That should take care of this.

I agree with you the dependency is unfortunate.

At least with any ROS 2 packages, we (I) won't be making that mistake again.

from abb.

Thanks!

from abb.

Done.

Should be part of the next sync.

from abb.