]> code.ossystems Code Review - openembedded-core.git/commit
kernel.bbclass: add non-santized kernel provides
authorBruce Ashfield <bruce.ashfield@windriver.com>
Fri, 6 Jul 2012 15:52:41 +0000 (11:52 -0400)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Mon, 9 Jul 2012 15:58:19 +0000 (16:58 +0100)
commit7be043178f5b9d16d9a06696bc0b96689f202a8d
tree7c9285ba64c08458f6e01e002b15be48215aca07
parent8a307af8253a5fdff51515fe01ef7b527fdad89f
kernel.bbclass: add non-santized kernel provides

If the kernel version string uses characters or symbols that
need to be santized for the package name, we can end up with a
mismatch between module requirements and what the kernel
provides.

The kernel version is pulled from utsrelease.h, which contains
the exact string that was passed to the kernel build, not
one that is santized, this can result in:

 echo "CONFIG_LOCALVERSION="\"MYVER+snapshot_standard\" >> ${B}/.config

 <build>

 % rpm -qp kernel-module-uvesafb-3.4-r0.qemux86.rpm --requires
update-modules
kernel-3.4.3-MYVER+snapshot_standard
 % rpm -qp kernel-3.4.3-myver+snapshot-standard-3.4-r0.qemux86.rpm --provides
kernel-3.4.3-myver+snapshot-standard = 3.4-r0

At rootfs assembly time, we'll have a dependency issue with the kernel
providing the santizied string and the modules requiring the utsrelease.h
string.

To not break existing use cases, we can add a second provides to the
kernel packaging with the unsantized version string, and allowing the
kernel module packaging to be unchanged.

   RPROVIDES_kernel-base += "kernel-${KERNEL_VERSION}"

 % rpm -qp kernel-3.4.3-myver+snapshot-standard-3.4-r0.qemux86.rpm --provides
kernel-3.4.3-MYVER+snapshot_standard
kernel-3.4.3-myver+snapshot-standard = 3.4-r0

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
meta/classes/kernel.bbclass