On Mon, Oct 10, 2011 at 2:08 PM, Loïc Minier <loic.minier@linaro.org> wrote:
On Mon, Oct 10, 2011, Deepti Kalakeri wrote:We rarely use a defconfig alone; however in the case of kernel .debs,
> 1) The board on which the hwpack can be booted
> 2) The hwpack creation timestamp includes the date in yyyymmdd format along
> with the time in hhmm format.
>
> The hwpack name does not include any defconfig related information, which
> was used to build the kernel.
> Do we need to use the defconfig name as well to be part of the hwpack name ?
> Is there any other information you would like to include in the hwpack name
> ?
> Or do we need to continue with the current hwpack names ?
you should find the corresponding config under boot/config-`uname -r`
in the .deb (dpkg-deb -x the kernel .deb to find the config).
(note that in the case of kernel CI we currently use pure defconfig
configurations)
What I asked deepti to work on is to make the CI hwpacks exported
through http://ci.linaro.org/kernel_hwpack/ to be better backtrack-able
to the actual CI job they are coming from.
Instead of exploding the hwpack name with more info, we could also
introduce a new directory level in the kernel_hwpack directory like:
kernel_hwpack/ci_job_name/HWPACK1,2,3
... and then leave the hwpack names as they are now. Maybe
improve the version to rather use the git describe version of
the kernel tree and not the kind of meaningless timestamp.
--
Alexander Sack
Technical Director, Linaro Platform Teams
http://www.linaro.org | Open source software for ARM SoCs