On May 26, 2011, at 12:02 AM, Darren Hart <dvh...@linux.intel.com> wrote:
> 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.
This sounds especially useful for automated testing of upstream. I'd be
interested in setting up a public daily build and test report in such a
configuration. Let me know if it would be redundant.
>
> Signed-off-by: Darren Hart <dvh...@linux.intel.com>
> Cc: Richard Purdie <richard.pur...@linuxfoundation.org>
> Cc: Koen Kooi <k...@dominion.thruhere.net>
> Cc: Jason Kridner <jkrid...@beagleboard.org>
> ---
> .../uboot/{u-boot_git.bb => u-boot_2011.03.bb} | 0
> 1 files changed, 0 insertions(+), 0 deletions(-)
> rename meta/recipes-bsp/uboot/{u-boot_git.bb => u-boot_2011.03.bb} (100%)
>
> diff --git a/meta/recipes-bsp/uboot/u-boot_git.bb
> b/meta/recipes-bsp/uboot/u-boot_2011.03.bb
> similarity index 100%
> rename from meta/recipes-bsp/uboot/u-boot_git.bb
> rename to meta/recipes-bsp/uboot/u-boot_2011.03.bb
> --
> 1.7.1
>
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
