Description
In our lab we currently have a pure Python library (https://github.com/ami-iit/ADAM) that was released on PyPI (https://pypi.org/project/adam-robotics/), and we would like to release on conda-forge (upstream issue: ami-iit/adam#26).
The problem is this library depends on the Python module urdf_parser_py, that is available in PyPI in the urdf-parser-py package (see https://pypi.org/project/urdf-parser-py/). The latest version of the urdf_parser_py module is anyhow also release in ROS2, in the urdfdom-py package. To permit to package adam on conda-forge and without creating possible incompatibility/clobbering problems with robostack's ROS2 package, my idea is to:
- Release the
urdf_parser_pypython module from https://github.com/ros/urdf_parser_py asurdfdom-pypackage in conda-forge (sorry for the confusion betweenurdf_parser_py/urdfdom-py, I just following the choice made when the library/repo were written) - Add in https://github.com/RoboStack/ros-humble/tree/main/additional_recipes a
ros-humble-urdfdom-pyrecipe that does not contain anything, at only has a run dependency on the urdfdom-py package from conda-forge with the same version, a bit like we did for Avoid ros-humble-octomap clobbering octomap #10
Do you think it make sense or there could be problems I am not considering? Thanks in advance! @Tobias-Fischer @wolfv