You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installing it as a ros2 mcap command might be a good option to avoid conflict with an Ubuntu universe debian package.
I personally think the developer experience of having the CLI available by default is more important than the reduced footprint of one less binary on the robot, given how much else ROS installs.
But if people feel strongly about reduced runtime robot footprint, then here is a concrete proposal:
New mcap_cli package that installs the ros2 mcap subcommand.
Make the mcap_cli package a dependency of rosbag2 metapackage (but not a dependency of rosbag2_storage_mcap), so that it is installed by default (see existing rosbag2 dependencies)
People who do not want the mcap CLI can install the specific dependencies of rosbag2 metapackage that they need (as they presumably would already be doing if they care about minimizing on-robot footprint)
The text was updated successfully, but these errors were encountered:
Copying over from ros-tooling/rosbag2_storage_mcap#47
Proposed plan from @amacneil:
The text was updated successfully, but these errors were encountered: