Release router tools artifact?

[jiridanek]

Options of distribution format

• PyPI release, python now uses wheels to distribute packages (new generation of python eggs), will depend on python-qpid-proton package (note that qpid proton cannot create multi-python-version wheel because swig does not support this, Support Python 3 stable API swig/swig#1009)
• skupper-router-tools RPM, which may or may not depend on skupper-router-server (see Fixed #186: Add rpm .spec to skupper-router project #189 (comment))
• PyOxidizer, https://github.com/indygreg/PyOxidizer, promises to be able to build a standalone portable executable, no personal experience with this
• Container image, users can either use the server image (but it is a large one, 800 MB or so in total), smaller tools-only image could be produced

Other considerations

• Compatibility, what version of tools supports what versions of the router? How will failures caused by version incompatibility look like to the user?
• ...

[jiridanek]

For the RPM approach, it would be helpful to be able to tuck in python-qpid-proton inside the router RPM package, probably into /usr/lib/skupper-router/python. https://www.alexhudson.com/2013/05/24/packaging-a-virtualenv-really-not-relocatable/