On Wed, Jun 15, 2011 at 2:56 PM, Zygmunt Krynicki < zygmunt.kryni...@linaro.org> wrote:
> I was writing it this morning. It actually pulls all of the branches that > compose lava and gives you an ability to install them in a managed > virtualenv instance. > > Great! > > 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. >> > > So there are three possible cases: > > 1) A component has no dependencies and runs from tree (awesome!) > 2) A component depends on something we make > 3) A component depends on something others make > > But what about where other non-python packages need to be installed for it to work properly? That was the main thing I was trying to sort out? Does the recipe have a rule to do this? In the case where post-install configuration is needed, does it point the user to instructions for how to do that? Thanks, Paul Larson
_______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
