W dniu 15.06.2011 22:49, Paul Larson pisze:
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?
For building this knowledge is contained in the source package. Nothing new or special here (we can build all the debs in pbuilder after all).
For development it will be provided by virtualenv (thanks to setup.py meta-data). The only thing that would not be provided are things that are not available on pypi such as usb utils for lava-test. This is a more complicated issue that I did not approach yet. We can observe the extreme when we consider that adb is something we kind-of require sometimes for some "components".
Thanks for pointing that out.
In the case where post-install configuration is needed, does it point the user to instructions for
how to
do that?
None of this is for end users. This is for developers of the lava stack and automatic testing of arbitrary collection of branches of said stack.
We _can_ and _should_ document how to use it in practice though and I plan to do that :-)
Thanks ZK