Sam Privett

Hey @esteve, I'm interested in helping out with this. Is there anything in particular you'd like help with?

I'll take a look, thanks :+1:

``` Run sudo pip3 install git+https://github.com/colcon/colcon-cargo.git error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you...

Draft PR is here https://github.com/ros2-rust/ros2_rust/pull/400

It is currently failing with ``` Run sudo pip3 install git+https://github.com/colcon/colcon-cargo.git error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where...

Yeah for now `--break-system-packages` is the path we've been using. Once `colcon-cargo` and `colcon-ros-cargo` are released on the build farm they should be apt installable removing the need for `--break-system-packages`...

That rust version is supposed to be the minimum supported version of rust that rclrs would work with. However, our [CI does not use this same version](https://github.com/ros2-rust/ros2_rust/blob/main/.github/workflows/rust.yml#L54) so there is...

Yeah, I think tying our minimum Rust version to what is shipped with Noble is reasonable if it helps reduce friction to get into the build farm. > boostrap rustc...

Okay, pretty cool, so this is a "bring your own cargo workspace" approach? What is the expected behavior of a workspace setup like this ``` . └── colcon_ws/ ├── Cargo.toml...

Ah yeah, I didn't word the second option well but #396 is exactly what I was referring to. We can close once that's merged.