circular dependency about bloom

[tfoote]

This is definitely something we need to catch. I'm not sure where we should be catching this, as bloom could potentially catch circular dependencies like the rospy, rosgraph, rostest one which are all intrarepo, but to check outside the repo is a problem. I think it would be more appropriate to check it at generation time as that's when we build the full dependency tree.

[wjwwood]

If this is to be caught in bloom, then I think the implementation of this
catch should potentially go in to catkin_pkg.

On Wed, Oct 3, 2012 at 9:27 AM, Tully Foote [email protected]:

This is definitely something we need to catch. I'm not sure where we
should be catching this, as bloom could potentially catch circular
dependencies like the rospy, rosgraph, rostest one which are all intrarepo,
but to check outside the repo is a problem. I think it would be more
appropriate to check it at generation time as that's when we build the full
dependency tree.

—
Reply to this email directly or view it on GitHubhttps://github.com/ros/bloom/issues/29#issuecomment-9112514.

William Woodall
Willow Garage - Software Engineer
[email protected]

[wjwwood]

The case where one package depends on itself is already caught in catkin_pkg.

The case where you want to check for cycles globally is non-trivial and really can't be realized without a global dependency database.

You could check that a list of packages (say from a multi package repository) do not depend on each other cyclically, but if anyone wants that check then open a ticket on catkin_pkg's issue tracker.