Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

move_base_msgs not included in melodic desktop_full #27

Closed
chrisl8 opened this issue Feb 13, 2019 · 3 comments
Closed

move_base_msgs not included in melodic desktop_full #27

chrisl8 opened this issue Feb 13, 2019 · 3 comments
Labels

Comments

@chrisl8
Copy link

chrisl8 commented Feb 13, 2019

Sorry to throw this here, I am not sure if it is the right place, but I'm hoping.

When I run rosinstall_generator desktop_full --rosdistro melodic --deps --tar > melodic-desktop-full.rosinstall the resulting .rosinstall file includes navigation_msgs/map_msgs, but NOT navigation_msgs/move_base_msgs

This seems like an oversight, but I do not understand the system well enough to know were to report this or who to ask.

@dirk-thomas
Copy link
Member

map_msgs is in desktop_full (or actually in desktop) because it is being used by rviz.

move_base_msgs isn't used by any of the packages in these meta packages and therefore not included. Only move_base and navigation uses that package and neither of them is part of desktop_full.

Please see REP 150 for more details.

@chrisl8
Copy link
Author

chrisl8 commented Feb 13, 2019

Thank you for the help!

If anybody had asked me, I would have said navigation was in one of the meta packages, but clearly I was wrong.

Now at least I understand why move_base_msgs is missing, and I can fix my issues by pulling and building navigation on top of desktop_full.

navigation seem like an integral package to almost any ROS setup, but I suppose that is a policy discussion, not a technical one.

@chrisl8 chrisl8 closed this as completed Feb 13, 2019
@dirk-thomas
Copy link
Member

If I remember correctly the reason why it is not included in e.g. the robot meta packages is that while there are numerous different navigation solutions in ROS the REP tries to avoid picking specific implementations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants