Revision history [back]

geometry_msgs package contains multiple msg types (see its wiki). Some of them, as you cited TwistStamped for example, uses std_msgs/Header (while some others don't same as you referred). Thus as a package, it depends on std_msgs.

Right now I don't have an access to fuerte but in groovy,

$ rospack depends geometry_msgs 
cpp_common
rostime
roscpp_traits
roscpp_serialization
genmsg
genpy
message_runtime
std_msgs

geometry_msgs package contains multiple msg types (see its wiki). Some of them, as you cited TwistStamped for example, uses std_msgs/Header (while some others don't same as you referred). Thus as a package, it depends on std_msgs.

Right now I don't have an access to fuerte but in groovy,

$ rospack depends geometry_msgs 
cpp_common
rostime
roscpp_traits
roscpp_serialization
genmsg
genpy
message_runtime
std_msgs

geometry_msgs package contains multiple msg types (see its wiki). Some of them, as you cited TwistStamped for example, uses std_msgs/Header (while some others don't same as you referred). Thus as a package, it depends on std_msgs.

Right now I don't have an access to fuerte but in groovy,

$ rospack depends geometry_msgs 
cpp_common
rostime
roscpp_traits
roscpp_serialization
genmsg
genpy
message_runtime
std_msgs

Update) I confirmed on fuerte indeed rospack depends geometry_msgs returns nothing, and in its manifest.xml no dependency is defined. Interesting. The history on github says:

 stripping depend and export tags from common_msgs manifests as msg dependencies are now declared in cmake and stack.yaml. Also removed bag migration exports

geometry_msgs package contains multiple msg types (see its wiki). Some of them, as you cited TwistStamped for example, uses std_msgs/Header (while some others don't same as you referred). Thus as a package, it depends on std_msgs.

Right now I don't have an access to fuerte but in groovy,

$ rospack depends geometry_msgs 
cpp_common
rostime
roscpp_traits
roscpp_serialization
genmsg
genpy
message_runtime
std_msgs

Update) I confirmed on fuerte indeed rospack depends geometry_msgs returns nothing, and in its manifest.xml no dependency is defined. The In the history on github @kwc says:

 stripping depend and export tags from common_msgs manifests as msg dependencies are now declared in cmake and stack.yaml. Also removed bag migration exports
stack.yaml.

That makes sense This explains why geometry_msgs can still refer to std_msgs w/o the dependency not being defined in manifest.