Relying only on environment variables is tricky for such things.
I remember when I built ROS for Yocto, there were so many meta-build systems involved that, at some point, the info got lost and then the download didn't work. I believe it had to do with the way python distutils were called from catkin, or something the like. Also, some version control systems like SVN and also some dependency resolution systems like maven don't look at the environment variables.
If possible, it would be preferable if we could have configuration variables for that directly within ament, which are filled from http_proxy and https_proxy by default. This way, they could be passed on to to the downstream tools in the proper way.
---
[Visit Topic](
https://discourse.ros.org/t/ament-build-with-proxy-setup/2913/5) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)