-
Notifications
You must be signed in to change notification settings - Fork 65
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
rospack depends on rosdep #63
Comments
Some verbs of Btw. you might not want to trust the GitHub search. It sometimes provides you only with incomplete results. E.g. in this case it didn't return you the cases where |
Oh blah, I thought I did check for rosdep2, but I was looking at other repos and must have gotten confused. Anyway, looks like the immediate affected methods are At a conceptual level, I can see rospack needing to be able to distinguish between catkin deps and system deps, but this still feels like a strange dependency to me, especially when it comes up at runtime— what is it that roslaunch and rosrun are doing which ultimately comes back as a complaint from rosdep about being uninitialized? |
I don't know what exactly you are invoking. I don't know of anything in |
Ah.. hmm. You're right that it isn't required for a trivial invocation. We see it on our platforms and in buildroots running unit tests. I will reopen the ticket when I get a concrete MWE for where I think there's a wrongful rosdep dependency. |
Just to follow up here, it's an issue with plugin discovery. Similar report here: The underlying issue is with |
There's some discussion here: #5 (comment)
And I can't actually find any instances of rosdep being needed by this code: https://github.com/ros/rospack/search?q=rosdep&type=Code
Is the dependency completely vestigial at this point? If so, can it be removed?
Our deployed robots are not development platforms; rosdep should not be necessary as a runtime dependency of ROS; we'd like to eliminate having to install and initialize it.
The text was updated successfully, but these errors were encountered: