Grey

For reference, there is now a [logging_demo](https://github.com/ros2-rust/ros2_rust/blob/main/examples/logging_demo/src/main.rs) that added during the async execution PR which I think covers all the features that this PR was meant to demonstrate.

@esteve it occurs to me that the vendored message packages could create a lot of confusion when building the `ros2_rust` repo in the same workspace as a ROS distro, which...

In the working group meeting today it was mentioned that we might not need the vendored messages if the build farm would generate the bindings for the message packages that...

> we could explore publishing some of the base message packages as crates I'm not particularly against this, but I can imagine us running into conflicts with crate names as...

Thanks for reporting this problem. We should fix the instructions to say that you should build your package in the same colcon workspace that rclrs and your message packages were...

I wouldn't be surprised if `cargo-manifest` has put out a new minor version which cargo's semantic versioning thinks is compatible with 0.2, so it's automatically using the newer version. If...

Can I check how you installed cargo-ament-build? I'm surprised that we're not seeing a problem in the [1.75 MSRV CI](https://github.com/ros2-rust/ros2_rust/actions/workflows/rust-minimal.yml?branch=main).

You're right, I misunderstood the direction of the problem. I've gotten too accustomed to needing to freeze old versions of crates when builds start to break.

> I suspect that the real solution however, would be to distribute colcon-cargo and colcon-ros-cargo as binaries through the buildfarm, was there any reason this wasn't done in the past?...

The [colcon installation page](https://colcon.readthedocs.io/en/released/user/installation.html) indicates that debians for colcon get distributed from both the ROS 1 and ROS 2 apt repo. The packagecloud repo is meant for users that don't...