ROS_ETC_DIR usage
I'd like to take advantage of the ROS_ETC_DIR in some packages, but I have a few points of confusion about it:
- My reading of REP-123 suggests that ROS_ETC_DIR should be
/etc/ros
(or/etc/ros/hydro
), but it's actually/opt/ros/hydro/etc/ros
. - When I have an overlay workspace, and I source the workspace's
devel/setup.bash
, ROS_ETC_DIR still just points to/opt/ros/hydro/etc/ros
- When I make the install space, I see
install/etc
get generated. However, when Isource install/setup.bash
, I still get ROS_ETC_DIR pointing to/opt/ros/hydro/etc/ros
. - In the install space, if I create a directory for my package, it is findable using
catkin_find mypackage --etc
Is the theory that in develspace, anything I would be putting in the etc
folder will just be in my source and thus findable that way? What about files which are templated or otherwise generated? Should they hang out in devel
or is a generated configuration file a sign that I am doing something wrong?