Ryan

ament_lint_xmllint could then automatically validate launch files in your repo are compliant to the schema. We already get warnings when migrating from ROS 1 to ROS 2 on your `package.xml`...

> 2\. python3 -m venv venv --system-site-packages --symlinks This doesn't work, still can't find `lark`, despite it being installed. ``` --- stderr: nav2_msgs Traceback (most recent call last): File "/home/ryan/Development/ros2_rolling/install/rosidl_generator_type_description/lib/rosidl_generator_type_description/rosidl_generator_type_description",...

> > > 2. python3 -m venv venv --system-site-packages --symlinks > > > > > > This doesn't work, still can't find `lark`, despite it being installed. > > ```...

Same for XML: ```xml ```

> i think we can come back to this PR after #771 is merged. Yay, 771 is merged! This is a great feature and would be very handy when connecting...

Could this be targeted for ROS2 Iron? The Dual-antenna GPS receivers are becoming more popular in the aerial industry.

> I suggested potentially including a `NavSatFixWithOrientation` kind of message that combines them, in case we want to add a new message instead of modifying an old one. A NavSatFix...

> if we respect OpenCV users then there should a timeframe for transition to avoid unwanted breaking of user code on OpenCV version upgrades. > > * 4.x: without regressions...

Is there any more feedback from the OpenCV team? Is there any desire to improve the CMake user experience for OpenCV5?

Since a change like this doesn't need to break ABI, it doesn't need to wait until opencv 5.