> > So having those requirements my goals were to build a tool that would be > useful for those two tasks: > 1) Daily development helper as a sort of CI tool. > 2) Monthly release helper > > So for purpose 1, if we wanted to use the same tool to make this easy, could we just do something like 'lava-ci project develop'? It seems to me, that on some things, this could be overkill, or not really make it that much simpler. For instance... in the case of lava-test you may want to also install python-apt, but there are other things like usbutils. In the case of the dispatcher, it can also run completely from the source branch. Except there are things like conmux that you would want to install, and configure to tell it how to get to your test machines. For situations like those, unless you have already thought of it here, I think it's no harder to just provide instructions for creating a development environment. However I'm well aware that other projects such as those dependent on the libraries you mention, and the lava-server piece can be somewhat trickier. How much of a stretch is it to extend this to cover case 1 as you mention, or do you feel for all of these it would be easier to provide a script in-tree to setup virtualenv + instructions for configuration to setup a development environment?
Thanks, Paul Larson
_______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
