Closed 130s closed 6 years ago
I don't think it is the responsibility of catkin_pkg
to print a warning here. A caller which expects such a cycle wouldn't be able to use the API without resulting in this error output.
The return value if the API is specifically designed to provide exactly the right information to the caller which contains the set of packages which are part of the cycle. So in my opinion this needs to be addressed on the caller side (in this case in catkin_tools
).
Closing in favor of using the existing return values to handle this in the calling location and print a warning there.
Issue Even when there are pkgs that include circular dependency,
topological_order_packages
returns a list without specifically trying to raise an attention. Because of that, call at some downstream functions that don't handle circular dependency fail without meaningful info (e.g. catkin/catkin_tools#430).Approach Print the name of packages that include circular dependency.
Output Sample
AFTER (notice there's WARNING)
TODO