On Tue, 7 Jun 2011 10:28:10 -0300, Christian Robottom Reis <k...@canonical.com> wrote: > > One very cheap thing we could do is to produce a report when building > > the hwpack that tells you which archive each binary package that was > > used came from. You can sort of do this now (assuming there aren't > > clashing versions), but it's a pain. Once you know that you can find the > > source package. So this is a general solution, but we can do much better > > in specific cases. > > That's a good idea.
https://bugs.launchpad.net/linaro-image-tools/+bug/794303 Pretty easy I think. > > Another cheap thing to do would be to dump the config from the kernel > > package in to the output dir, so you can see the config without having > > to download the hwpack or produce an image. This can be useful, much > > like the new .manifest that lists the packages included and their > > versions is useful if you want to know if the new hwpack build picked up > > the fix for some bug in the latest upload. > > That's also a good idea. +1 for JFDIing these parts of the solution. https://bugs.launchpad.net/linaro-image-tools/+bug/794304 a bit trickier, but as I say in the report some work that Mattias is doing may help here. We'll try and pick these up for this month's release. Thanks, James _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
