Ask Your Question

migrating to ros: duplicate package names

asked 2011-06-18 12:49:29 -0500

btown gravatar image

Hi all,

I'm trying to migrate our robotics team's existing software, which uses a custom qmake-based build system, to ROS, but I'm running into a problem where packages have the same name, but are in different stacks. For Instance, we have unrelated code in:


I've tried making RobotA and RobotB stacks, but then rospack find Vision only sees RobotB/Sensors/Vision. Is there a way to make the ROS build system and bash tools look inside a specific stack, or directory? I'd rather not have to redesign the entire repository. It makes sense that this would be possible... what if you wanted to integrate somebody else's stack, but they used a name that you also used?


edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2011-06-18 14:25:07 -0500

dornhege gravatar image

I'm not sure, if that achieves what you want, but you can adjust your ROS_PACKAGE_PATH. If you include either RobotA or RobotB, the ros tools will only find the vision package in that stack.

Using both at the same time under the same name is not possible.

edit flag offensive delete link more


Thanks! I was afraid of that, but I'll just make a script that changes the package path.
btown gravatar image btown  ( 2011-06-18 14:54:39 -0500 )edit

answered 2011-06-19 01:11:05 -0500

joq gravatar image

ROS stack and package names are global to the entire ROS universe.

It will be much less confusing and annoying to give all your stacks and packages unique names, like robot_a_vision and robot_b_vision (lower case names are preferred).

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2011-06-18 12:49:29 -0500

Seen: 521 times

Last updated: Jun 19 '11