Merge lp://qastaging/~vishalbhoj/linaro-image-tools/hwpack-from-boottarball into lp://qastaging/linaro-image-tools/11.11

Will /boot/config perhaps conflict with something other than the "hwpack"? Also, it'd be good to have tests for this to ensure it works properly and that we don't break it in the future.

Hi Vishal,

overall it looks good.

Looking at the code, I was thinking about where the boot tarball hwpack will be picked up. As it has been implemented now, the hwpack from the boot tarball will take priority, even if we pass one on the command line. What if someone wants to test different hwpack values, but using the same tarballs? Would it make sense to check for the hwpack in the boot tarball before using the one passed on the command line? It is not mandatory, it works also in this way, and if it is OK for you it is not a problem.

Testing that part might be trickier than expected actually: the file is not usuable as a module, so we cannot test parts and bits of it.

We might add a check in the 'linaro_image_tools/utils.py' file under the 'additionl_android_option_checks' function, adding some logic there. In that way, we can easily test that function, as we are already doing: the tests are located in 'linaro_image_tools/tests/test_utils.py'. It might be also necessary to add a new function to the 'utils.py' module, just to check the path in order to make it testable.

If you need any help to move this forward, please feel free to ping me on IRC.