Best practices for releasing a ROS package with a dependency on a pip package
I'm trying to release a packagethat depends on pynput, which is resolved to pip by rosdep (https://index.ros.org/d/pynput-pip/).
After getting the package included to the distribution.yaml, the test build failed on build.ros.org
It turns out that ROS buildfarm does not support dependencies which are resolved to pip packages by rosdep (https://github.com/ros-infrastructure...).
Towards the end of the discussion it is mentioned that a workaround is to package pip dependency/ies as a deb package/s. This is a lengthy process as well, as the packages have to be included to distributions with their own release cycles and policies.
I think this is not a lonely case as there are many python packages listed in https://github.com/ros/rosdistro/blob..., that only resolve to pip (e.g. python-numpy-quaternion-pip, python-numpy-stl-pip, python-objectpath-pip ...).
What are the best practices for releasing such a ROS package? Finding someone to maintain package in Ubuntu and wait until it gets added to their repositories? Generating a deb package and adding it to launchpad or some other service for package building and hosting? Generating a deb package and add it to ROS repository (how)?
