The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Probably the behavior of rosmake could be changed such that rosmake B is translated to rosmake B1 (In general all packages in the given stack). The stack-to-stack dependency should maybe only be used for packaging, not building.
Given that stacks are defined as an atomic unit of release, not an atomic unit of build, that would make sense.
So you can always raise a ticket and see what the rosmake maintainers will have to say about it.
Which package goes into which stack should also be a releasing decision.
One way to think about it is: If one day there was a debian package for stack B, and users apt-get install it, should this also automatically install A2 (and thus also all of the dependencies of A2)?
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.
