ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

The best practice is to get the package released upstream as an Debian package that will then get imported into Ubuntu. As you mentioned this is a long process.

Most people using pip only rules understand that they can only use their package from source.

There are ways to bundle pip packages into ROS packages that can then be released. If you do that you're committing to maintaining it. Such as catkin_virtualenv and catkin_pip

An other option is to embed the library inside your package. Make sure to be clear about licensing etc and hide the implementation so it doesn't cause conflcts with potentially other versions.

All of this comes down to that someone has to be willing and able to maintain it for all the use cases.

The best practice is to get the package released upstream as an Debian package that will then get imported into Ubuntu. As you mentioned this is a long process.

Most people using pip only rules understand that they can only use their package from source.

There are ways to bundle pip packages into ROS packages that can then be released. If you do that you're committing to maintaining it. Such as catkin_virtualenv and catkin_pip

An other option is to embed the library inside your package. Make sure to be clear about licensing etc and hide the implementation so it doesn't cause conflcts with potentially other versions.

All of this comes down to that someone has to be willing and able to maintain it for all the use cases.

And note that if there already is a version in the apt repositories you should use that one and not try to override it with a newer version from pip as that has the potential to break many other users.