summaryrefslogtreecommitdiff
path: root/meta-rt/conf
diff options
context:
space:
mode:
authorDarren Hart <dvhart@linux.intel.com>2011-05-25 20:47:05 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-05-27 16:36:08 +0100
commitf788d4b503ecc6600612746c4936dfb9393e237c (patch)
tree6087325aa3347fcfbe8b21fd4d77f4a35b8018d9 /meta-rt/conf
parentc7a198d7472b4767047dbbfeecb4d941055262b3 (diff)
downloadopenembedded-core-f788d4b503ecc6600612746c4936dfb9393e237c.tar.gz
openembedded-core-f788d4b503ecc6600612746c4936dfb9393e237c.tar.bz2
openembedded-core-f788d4b503ecc6600612746c4936dfb9393e237c.tar.xz
openembedded-core-f788d4b503ecc6600612746c4936dfb9393e237c.zip
u-boot: rename u-boot_git.bb to u-boot_${PV}.bb
In order to facilitate reuse of the oe-core u-boot recipe, there needs to be some assurance that the oe-core version won't change without a clear indicator to people extending it. By renaming the recipe to include its version string instead of "git", BSP layers can extend a specific base version of u-boot, ie. u-boot_2011.03.bbappend. When 2011.06 becomes available, we can create that file without instantly breaking all the BSPs depending on oe-core version of the recipe. As a matter of policy I would recommend we not carry more than 2 versioned u-boot recipess at any given time. This will provide BSP layers time to migrate to the newer version, without cluttering oe-core with numerous stale versions of u-boot. We may decide later to resurrect u-boot_git.bb as an AUTOREV recipe to faciliate upstream development on u-boot in the oe environment. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Koen Kooi <koen@dominion.thruhere.net> Cc: Jason Kridner <jkridner@beagleboard.org>
Diffstat (limited to 'meta-rt/conf')
0 files changed, 0 insertions, 0 deletions