Contents
SIG Coordinator:
Topics:
- catkin
- rosbuild
- bloom
- rosinstall / wstool
Members:
- Tully Foote
- Daniel Stonier
- Jack O'Quin
- Lorenz Mösenlechner
- Florian Weisshardt
- Stéphane Magnenat
- Dirk Thomas
- William Woodall
- Mike Purvis
Mailing list:
Proposed new features
- Tully: Separate catkin build and release infrastructure.
(Jack) With catkin, we seem to have lost some ability to conveniently list a package's direct and indirect dependencies. Let's provide some tools to help out.
(Jack) Distinguish binary from source packages, with separate build dependencies and runtime dependencies. (Probably a long-term discussion, but it should not be overlooked.)
(Stéphane) Improve the usability of debbuild report pages by documenting the steps and clearly telling the user the status of each stack on each platform.
(Mike) Further to that, I wonder if the status page could also show information like whether the package is generating docs, whether it has a wikipage, and whether it's part of CI. This stuff is not directly related to the building of debs, but it all serves as a thermometer to tell how much care a package has received.
(Lorenz) Extend the signature of the _generate_module_<language> cmake macro to also pass the list of input files. roslisp message generation is still really hacky because asd file generation (the lisp equivalent to a makefile) needs a list of all input files. I would like to get rid of that hack, but the only way to do that is to extend the cmake macro.
(Lorenz) Clarify if rosmake should be removed and when. Clarify which stacks should be catkinized and which not and how to deal with packages that only contain launch files and dependencies, e.g. the pr2_bringup package.