When building ros_comm packages from tarballs (downloaded individually from github) into a devel space, the resulting ros environment hooks will incorrectly set the ROS_ROOT. It is incorrect because it assumes that the roslib package is located relatively to other packages in the ros_comm repository. This relative layout is changed when the packages are released and segmented by bloom.
When building ros_comm packages from tarballs (downloaded individually from github) into a devel space, the resulting ros environment hooks will incorrectly set the ROS_ROOT. It is incorrect because it assumes that the roslib package is located relatively to other packages in the ros_comm repository. This relative layout is changed when the packages are released and segmented by bloom.