On 06/01/2011 10:21 PM, Somebody in the thread at some point said:
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.
At least for the config,
CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y
gets you a gzip of the config used in the kernel body readable by scripts/extract-ikconfig externally, and readable at runtime down /proc/config.gz. (static extract script is useful in the case the kernel doesn't boot or stay up long enough to query at runtime). That's more tightly bound to the actual kernel than doing it in packaging only.
My build scripts put the git branch in the uname -r, the make process already puts the git HEAD hash in there; packaging can do the same.
Nowhere says which repo was used at the moment. However a lot of bug reports just talk about packagenames like blah-1003 leaving the reader clueless about where to get the package let alone what it was built from.
If CONFIG_IKCONFIG_PROC was used everywhere, we / the packaging process could leverage that to add a dummy Kconfig like CONFIG_BUILD_SOURCE="git://..." and have it all available cleanly just from the uImage or at runtime.
-Andy