ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange

Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

Unless I misunderstand you, metapackages don't work that way (they are not stacks). They are essentially a way to group a number of packages and make them easily installable by only installing the metapackage. Dependency resolution then pulls in the others.

In the original design, metapackages didn't even have a CMakeLists.txt.

Do you have any specific reason for such a directory layout?

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.

Powered by Askbot version 0.10.2