On Wed, Jun 01, 2011 at 05:21:14PM -0400, James Westby wrote:
I don't think we should be looking to attribute the provenance of every line of source that ends up in the hwpack in one report, we just need to shorten the chain to find the information that you care about.
That is a very good point, and a better statement of my intent.
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.
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.