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
{{ message }}
This repository was archived by the owner on Jun 25, 2020. It is now read-only.
foreach commands should be able to access the internal wstool variables, such as the root directory of the workspace , and the items being iterated over : the scmtype, local-name and uri.
Currently a wstool foreach command needs to do wstool info . --only scmtype,localname,uri to get this information, and separately wstool info --root if it doesnt want to derive the root from the localname.
This should be done using substitution variables in the command line, so that non-ros-aware commands can be used with wstool; .e.g
A simpler solution is to stuff this information into ROS_* environment variables, so that ros-aware tools can easily obtain these values without invoking wstool info
foreachcommands should be able to access the internal wstool variables, such as the root directory of the workspace , and the items being iterated over : the scmtype, local-name and uri.Currently a wstool foreach command needs to do
wstool info . --only scmtype,localname,urito get this information, and separatelywstool info --rootif it doesnt want to derive the root from the localname.This should be done using substitution variables in the command line, so that non-ros-aware commands can be used with wstool; .e.g
wstool foreach --git git clone -o upstream "{uri}" "{localname}"(That solves #59 ;-)
A simpler solution is to stuff this information into
ROS_*environment variables, so that ros-aware tools can easily obtain these values without invokingwstool info