Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [pull-oe-uboot 2/2] u-boot: rename u-boot_git.bb to u-boot_${PV}.bb
Date: Thu, 26 May 2011 06:52:15 -0700	[thread overview]
Message-ID: <4DDE5B0F.5080901@linux.intel.com> (raw)
In-Reply-To: <6EC98D6A-BEF1-468A-A69B-7CBF4EAB28BA@beagleboard.org>



On 05/26/2011 12:58 AM, Jason Kridner wrote:
> On May 26, 2011, at 12:02 AM, Darren Hart <dvhart@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.

That is the sort of thing this caters to, yes. And no, I don't think
your testing in this way would be redundant - at least not with respect
to anything I'm doing.

--
Darren

> 
>> 
>> 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> --- .../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

--
> 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel



      reply	other threads:[~2011-05-26 13:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26  5:01 [PATCH 0/2] u-boot updates to make it more bbappend friendly Darren Hart
2011-05-26  5:02 ` [pull-oe-uboot 1/2] u-boot: remove UBOOT_MACHINE and COMPATIBLE_MACHINES Darren Hart
2011-05-26  7:47   ` Jason Kridner
2011-05-26 13:50     ` Darren Hart
2011-05-26 14:08       ` Chris Larson
2011-05-26 10:50   ` Phil Blundell
2011-05-26 14:37     ` Richard Purdie
2011-05-26 16:18       ` Phil Blundell
2011-05-26 17:46         ` Darren Hart
2011-05-27 14:04           ` Phil Blundell
2011-05-27 15:06             ` Darren Hart
2011-05-27 15:11               ` Phil Blundell
2011-05-26  5:02 ` [pull-oe-uboot 2/2] u-boot: rename u-boot_git.bb to u-boot_${PV}.bb Darren Hart
2011-05-26  7:58   ` Jason Kridner
2011-05-26 13:52     ` Darren Hart [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DDE5B0F.5080901@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox