Hi all,

I recently encountered a problem with importing components into deployer.
My work-flow (using catkin workspaces) involve having multiple instances of
the "same" component in RTT_COMPONENT_PATH. I expected that it will works
like UNIX PATH and will load load component which is first in path. But it
loads all copies of the component and the copy which is actually last in
path is available in deployer.

The fix is actually quite trivial, you just need to break loading loop
after finding first valid package.

Could the behaviour of ComponentLoader be altered to work as expected ?
Does anyone relay on this (strange) behaviour ?

Best Regards,
Konrad Banachowicz