You mean if I am going to install a client tool (cli) for example cli for scheduler, I will get the scheduler install as well ? Do I understand you well ?
BR
/Chi Thu On 28 March 2012 07:11, Paul Larson paul.larson@linaro.org wrote:
On Mon, Mar 26, 2012 at 3:56 PM, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
W dniu 26.03.2012 22:47, Paul Larson pisze:
I think the obvious concern for me here is that now we would be proposing to require a growing stack of web components, django, etc in order to just get a cli tool to submit a job. That seems like quite a lot of overhead for such a simple thing. I'm a little surprised you wouldn't rather group all the cli tools together. Also, from the BP summary, it's not clear to me what the benefit is that you are trying to achieve.
You misunderstood my proposal. The dependencies are separate. The technique I'm using creates extras, optional components of a package that have additional dependencies.
In this case lava-dashboard-tool would be a transitional package that depends on lava-dashboard [tool]
It would not pull django ;-)
Transitional package? are you talking about debian packages here?
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation