[quote="kyrofa, post:12, topic:7072"]
Huh. Am I weird for expecting colcon to be available after installing ros-crystal-ros-base? I had to install python3-colcon-ros manually. I dont see that documented anywhere, but perhaps I glossed over it. Just `apt-cache search` 'd and installed the thing that seemed to make sense.
[/quote]
None of the packages in ROS 2 have a dependency on the colcon build tool. This is sort of nice since production systems don't necessarily need build tools so ROS 2 is one step closer to minimal production environments if the functionality to split out development info from runtime libraries is contributed.
[quote="kyrofa, post:12, topic:7072"]
**Update** : theres also no `--packages-select` option supported in the colcon that I installed. This option is suggested in the tips section of [the colcon tutorial](
https://index.ros.org/doc/ros2/Colcon-Tutorial/) as well as [readthedocs](
https://colcon.readthedocs.io/en/released/migration/catkin_make_isolated.html) for colcon. Am I missing something obvious?
[/quote]
The [Linux development instructions](
https://github.com/ros2/ros2_documentation/blob/master/Linux-Development-Setup.rst#install-development-tools-and-ros-tools) cover the colcon package installation with `python3-colcon-common-extensions`. The package name isn't my favorite. (My preferred color of the bikeshed is `colcon-sensible` :wink:) but because colcon is primarily implemented via plugins to the core colcon package and usable beyond the ROS ecoystem, the [colcon-ros](
https://github.com/colcon/colcon-ros) package includes only the packages needed to build ROS packages and not any of the creature comfort plugins that you might also want. Hence colcon-common-extensions to wrap them both.
[quote="kyrofa, post:12, topic:7072"]
Definitely feel like that should have been handled for me by installing ros-base, or some sort of colcon metapackage at least (perhaps simply called `python3-colcon` ?).
[/quote]
I don't agree that colcon or any tools needed only at build time ought to be in `ros-base`. But I also see where the suggestion is coming from and I think a `base-devel`- or `build-essential`-like metapackage which could include everything necessary to build `ros-base` from source is a reasonable metapackage to propose. As well as the inclusion of said package in `ros-desktop`. The metapackage contents are specified in [REP-2001](
http://www.ros.org/reps/rep-2001.html) and you can open pull pull requests against the [ros-infrastructure/rep](
https://github.com/ros-infrastructure/rep) project to propose modifications.
---
[Visit Topic](
https://discourse.ros.org/t/ros-2-crystal-clemmys-call-for-testing-and-package-releases/7072/14) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)