G.A. vd. Hoorn

Yeah. And that is exactly why the current implementation is as it is right now ..

Related: #144. Yaml with substitution args or even the new [yaml support in xacro](http://wiki.ros.org/xacro#YAML_support) could be approaches to consider here. Configuring the xacro macro from a yaml file completely would...

@ipa-nhg @ipa-led @miguelprada

See my https://github.com/UniversalRobots/Universal_Robots_ROS_Driver/issues/84#issuecomment-642202800.

They're broken in `melodic-devel-staging`, yes. That is known and will be fixed. I decided not to fix them by not including #467 in #501.

That would be appreciated. I have some pretty specific ideas about those configuration pkgs though, so it may take a bit of back-and-forth. The MSA v2 does some strange things...

I just followed the instructions [in the readme](https://github.com/UniversalRobots/Universal_Robots_ROS_Driver/blob/777560cf735d33c706a1e5cfc6a8daeffc6a0b54/README.md#building) of `Universal_Robots_ROS_Driver` in a clean Docker container (copy-pasting every line) which resulted in a successful build. Does that not work for you?

No, not necessarily. @fmauch syncs them every now and then when it is necessary or makes sense to him, but there is no direct link.

I'm confused as to why you link to a `build.ros.org` job. `industrial_ci` is not used there.

I haven't had time to test it yet, but ever since I've come across [nektos/act](https://github.com/nektos/act) I've wanted to test it with `industrial_ci`.