package available only on pip blocks debian package installation
I have a package <my-package> in which a python package is a run dependency. It is only available on pip for some reasons. It is in the python.yaml in rosdistro.
I have packaged <my-package> in a debian format. When I want to install with apt-get install
, it of course complains that I have unmet dependencies to install the python dependency with apt:
The following packages have unmet dependencies:
<my-package> : Depends: <python-dependency1> but it is not installable
Depends: <python-dependency2> but it is not installable
This can also happen with packages available on apt repositories but with a lower version than which we need.
What is the best way to handle this? Here it is for private application, but it could similar for public repositories.
Should I package the python dependency myself for internal purposes (I think it's the easiest but not the nicest since pip package don't have the python-
prefix like the apt ones, which can lead to confusion)
Thanks