On Mon, 1 Oct 2018 at 10:24, Neil Williams neil.williams@linaro.org wrote:
Is there any reason why lava is stuck with debian? Why not package it as pip package and make distro agnostic?
This is covered in the docs. LAVA has dependencies which cannot be provided by pip and it has functionality which pip cannot support.
Could you point me to the docs?
https://master.lavasoftware.org/static/docs/v2/first-installation.html#softw...
Also https://master.lavasoftware.org/static/docs/v2/debian.html#developing-lava-o... and https://master.lavasoftware.org/static/docs/v2/development-intro.html#develo...
OK, so from what I read here, there are 2 reasons listed: 1. dependencies not available in pip (guestfs) There already is a python package available for it here: http://download.libguestfs.org/python/ as described in the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1075594.
2. daemons and system-wide configuration is correctly updated I'm not sure what exactly that means but most likely can be done for example with ansible role that corresponds to proper lava version. This would allow to have parts of lava in containers and have easier development process.
I didn't say it will be a merge request. The main part of the REST API can be supported as there is a debian package for it "python3-djangorestframework". Filtering part will be a separate branch "for the brave ones"
I can't recommend maintaining a permanent fork. It isn't that much work, probably, to get this package into Debian.
I'm not signing up to be a package maintainer (been there once long time ago). I can ask the author, but if the package wasn't created so far I don't have much hopes. Beside that, the branch would be just 1 patch long.
milosz