You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our use case is in CI we use containers whose apt package cache is often stale, causing rosdep install to eventually fail unless apt-get update has run recently.
I propose that rosdep install should have an --update flag that will refresh the package cache if the backend package manager supports that. The equivalent of running apt-get update && rosdep install foo.
The text was updated successfully, but these errors were encountered:
Since rosdep is acting as a wrapper for apt install foo, I was thinking it made sense to wrap the requirement for that underlying command to succeed (apt update). However, I'm pretty new to using rosdep at all so I'll take your word for it if that doesn't fit the intended use of rosdep.
rosdep not only manages apt, but also other package managers, such as rpm, brew, etc.
While I agree adding an option to update the cache (e.g. --update-cache) would be nice, we'll need to add functions for all the package managers (which has OSs that I don't have access to).
tldr: it's quite complicated to implement properly, let alone testing it.
Our use case is in CI we use containers whose apt package cache is often stale, causing
rosdep install
to eventually fail unlessapt-get update
has run recently.I propose that
rosdep install
should have an--update
flag that will refresh the package cache if the backend package manager supports that. The equivalent of runningapt-get update && rosdep install foo
.The text was updated successfully, but these errors were encountered: