-
Notifications
You must be signed in to change notification settings - Fork 171
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
Update the database of only a single ROS distribution #723
Comments
Would it make sense for rosdep to default to the ROS_DISTRO env if the arg is unset, same as the |
Yeas I was going back and forth on that as it is not uncommon to have a given distro sourced by default but you want to update all the database.
And in that case I wont have the latest state of dashing packages in the db to perform the install. So my preference would be to not change the behavior unless an argument is passed. |
@nuclearsandwich @wjwwood gentle ping. Do you have any feedback on this? |
Makes sense to me. 👍 for a pull request for this feature.
I agree. |
feature request / question: would it be possible to specify to rosdep we want to update the database of a single ROS distribution?
Rationale: Often rosdep is slow to run and the more active ROS (1 and 2) distributions the longer it takes to run. Ignoring the EOL distros helped a great bit but it seems like performace would be even better with a single ROS distribution to process.
maybe it could be done if the rosdistro argument is explicitly used
rosdep update --rosdistro kinetic
, or maybe a different flag--only-selected-rosdistro
?Also it would override the eol flag compared to currently even if you specify explicitly an eol distro it doesnt get updated if it's eol
The text was updated successfully, but these errors were encountered: