The decision between stack vs package is a tough one. It depends on how many features are desired and if there are external dependencies.
On Fri, May 21, 2010 at 9:35 PM, Tully Foote <tfoote@willowgarage.com> wrote:Good idea. I hadn't thought of that. I was imagining a new package
> With regards to a location of a potential GPS message within the ROS package
> ecosystem, as the maintainer of common_msgs this seems like a strong
> candidate for inclusion in the sensor_msgs package.
defining both the messages and some utility functions.
Putting just the messages in sensor_msgs is better. There might end up
being two or three messages, depending on how people decide to
structure it.
I just realized that Ken Tossell already has a gps_common package in
> As for the library components doing a package proposal for gps_common would
> be a good idea.
the umd-ros-pkg (University of Maryland). Looks like it only has a
message definition right now.
Whether we call it that or something similar, should it be a separate
stack or part of some existing one?
--
joq
_______________________________________________
ros-users mailing list
ros-users@code.ros.org
https://code.ros.org/mailman/listinfo/ros-users