loading components with ROS workspace overlays

I'm trying to get a workflow where I have code installed to the system and then checkout just the components I need to modify, compile, run, etc. Using catkin and ROS workspaces, this is fairly easy to do using overlays. However, I have run into a problem with having multiple versions of the same Orocos component libraries in my RTT_COMPONENT_PATH.

After I build and source my freshly-built workspace and startup, I startup a new rttlua session. I try loading my component with:

I'm trying to get a workflow where I have code installed to the system and
then checkout just the components I need to modify, compile, run, etc. Using
catkin and ROS workspaces, this is fairly easy to do using overlays.

I think this is a common use case and needs to be supported in a standard way.

However, I have run into a problem with having multiple versions of the same
Orocos component libraries in my RTT_COMPONENT_PATH.

After I build and source my freshly-built workspace and startup, I startup a
new rttlua session. I try loading my component with: