Sam Privett

There is a really nice starting point being added in https://github.com/ros2-rust/ros2_rust/pull/417. We should expand this to cover the various build tools and their responsibilities with actually building the generated rust...

## Automatically upload ROS 2 messages to crates.io as semver'd packages. I took a look at the [semver](https://crates.io/crates/semver) crate, which is the crate that implement Cargo's interpretation of Semantic Versioning....

It is almost a year from when I first opened this issue and I think that calls for some updates. Listing out the potential solutions remaining for investigation with where...

Double check that you've got `colcon-ros-cargo` installed, and [rosidl_rust](https://github.com/ros2-rust/rosidl_rust/tree/main) needs to be built and sourced in your `ros2_ws/`. I think this is essentially the same issue you saw here https://github.com/ros2-rust/ros2_rust/issues/472...

Hi @George-Gi, this is due to our complex message generation and consumption pipeline. When you put `std_msgs = "*"` in your `Cargo.toml`, there should be an accompanying `.cargo/config.toml` file in...

You don't need to clone the whole ros2_rust repo, you can pull `rclrs` from crates.io via your crates Cargo.toml. But at the moment, the `rosidl_rust` package (which includes `rosidl_generator_rs`) needs...

Do any other rcl libraries do this? I couldn't find anything for rclcpp on docker hub

So I'm trying to understand our message pipeline thoroughly. I'm taking a look at [colcon-ros-cargo](https://github.com/colcon/colcon-ros-cargo) currently. This is the colcon plugin that will ultimately call `cargo build` for packages that...

This LGTM, we can address anything more in follow up PRs. Thanks @nwn!

I also think we should look into creating a client builder instead of proliferating `create__` functions.