summaryrefslogtreecommitdiff
path: root/meta/classes/lib_package.bbclass
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2011-06-08 15:33:02 -0400
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-06-14 13:15:52 +0100
commit576c87349a72a94357014ff29f55db692903ed80 (patch)
tree9f75e3216dbd8a45d460bbecfed129bd043530cf /meta/classes/lib_package.bbclass
parent6625936c011aa939e60041dc6be9850e925a6cc3 (diff)
downloadopenembedded-core-576c87349a72a94357014ff29f55db692903ed80.tar.gz
openembedded-core-576c87349a72a94357014ff29f55db692903ed80.tar.bz2
openembedded-core-576c87349a72a94357014ff29f55db692903ed80.tar.xz
openembedded-core-576c87349a72a94357014ff29f55db692903ed80.zip
linux-yocto: rename recipes to explicitly indicate version
The existing recipe names for the linux-yocto kernel builds worked well when there was a single, or two versions of the kernel available. But with the impending kernel updates and retirement of older kernels, the re-use of the same recipes for different kernel versions violates the principle of least surprise. To address this, the recipes are being renamed as follows: linux-yocto_git.bb -> linux-yocto_2.6.37.bb linux-yocto-stable_git.bb -> linux-yocto_2.6.34.bb There continue to be versionless recipe names that feed into versioned recipes at the appropriate points. They are: linux-yocto-dev.bb (tracking the latest yocto dev kernel) linux-yocto-korg_head.bb (tracking korg kernels) There are no existing users of linux-yocto-stable in the master branches to convert to the new naming, so these changes work in isolation. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'meta/classes/lib_package.bbclass')
0 files changed, 0 insertions, 0 deletions