Howto pin u-boot to a version supplied by oe-core

Howto pin u-boot to a version supplied by oe-core

[Andreas Mueller]

Hi,

for gumstix overo I am in the lucky situation that vanilla u-boot v2011.03 ( and 
maybe later version too ) meets my needs.

My current approach (in angstrom environment) was quick but poor: I simply 
copied here and there without reusing anything [1].

To improve I checked u-boot_2011.03 shipped by oe-core and think that one 
exactly builds what I need - without bbappend.

So I tried in overo.conf to pin by "PREFERRED_VERSION_u-boot=":

1. "2011.03"
2. "v2011.03"
3. "v2011.03+git19b54a701811220221fc4d5089a2bb18892018ca"
4. "v2011.03+git7+19b54a701811220221fc4d5089a2bb18892018ca"

got messages like 
NOTE: preferred version 2011.03 of u-boot not available (for item u-boot)
NOTE: versions of u-boot available: git 
v2011.03+git7+19b54a701811220221fc4d5089a2bb18892018ca 
v2011.06+git7+b1af6f532e0d348b153d5c148369229d24af361a
NOTE: Resolving any missing task queue dependencies
NOTE: preferred version 2011.03 of u-boot not available (for item u-boot)
NOTE: versions of u-boot available: git 
v2011.03+git7+19b54a701811220221fc4d5089a2bb18892018ca 
v2011.06+git7+b1af6f532e0d348b153d5c148369229d24af361a
NOTE: preferred version 2011.03 of u-boot not available (for item u-boot-dev)
NOTE: versions of u-boot available: git 
v2011.03+git7+19b54a701811220221fc4d5089a2bb18892018ca 
v2011.06+git7+b1af6f532e0d348b153d5c148369229d24af361a

and builds of
meta-texasinstruments/recipes-bsp/u-boot/u-boot_git.bb


How can I get the desired oe-core u-boot recipe pinned to reduce code 
redundancies?

Cheers

Andreas

[1] https://gitorious.org/schnitzeltony-oe-meta/meta-
gumstix/trees/master/recipes-bsp/u-boot

Re: Howto pin u-boot to a version supplied by oe-core

[Khem Raj]

On Thursday, August 04, 2011 12:11:51 AM Andreas Mueller wrote:
> Hi,
> 
> for gumstix overo I am in the lucky situation that vanilla u-boot v2011.03 (
> and maybe later version too ) meets my needs.
> 
> My current approach (in angstrom environment) was quick but poor: I simply
> copied here and there without reusing anything [1].
> 
> To improve I checked u-boot_2011.03 shipped by oe-core and think that one
> exactly builds what I need - without bbappend.
> 
> So I tried in overo.conf to pin by "PREFERRED_VERSION_u-boot=":
> 
> 1. "2011.03"
> 2. "v2011.03"
> 3. "v2011.03+git19b54a701811220221fc4d5089a2bb18892018ca"
> 4. "v2011.03+git7+19b54a701811220221fc4d5089a2bb18892018ca"
> 
> got messages like
> NOTE: preferred version 2011.03 of u-boot not available (for item u-boot)
> NOTE: versions of u-boot available: git
> v2011.03+git7+19b54a701811220221fc4d5089a2bb18892018ca
> v2011.06+git7+b1af6f532e0d348b153d5c148369229d24af361a
> NOTE: Resolving any missing task queue dependencies
> NOTE: preferred version 2011.03 of u-boot not available (for item u-boot)
> NOTE: versions of u-boot available: git
> v2011.03+git7+19b54a701811220221fc4d5089a2bb18892018ca
> v2011.06+git7+b1af6f532e0d348b153d5c148369229d24af361a
> NOTE: preferred version 2011.03 of u-boot not available (for item
> u-boot-dev) NOTE: versions of u-boot available: git
> v2011.03+git7+19b54a701811220221fc4d5089a2bb18892018ca
> v2011.06+git7+b1af6f532e0d348b153d5c148369229d24af361a
> 
> and builds of
> meta-texasinstruments/recipes-bsp/u-boot/u-boot_git.bb
> 
> 
> How can I get the desired oe-core u-boot recipe pinned to reduce code
> redundancies?

there is one u-boot recipe u-boot_2011.06.bb which is in both meta-ti
and oe-core layers but otherwise they have different versions

in anycase what you need to lock is PV and the recipes in oe-core has 

u-boot_2011.03.bb:PV = "v2011.03+git${SRCPV}"
u-boot_2011.06.bb:PV = "v2011.06+git${SRCPV}"

So what you need is 

PREFERRED_VERSION_pn-u-boot = "v2011.03+git%"

-Khem

Re: Howto pin u-boot to a version supplied by oe-core

[Andreas Mueller]

On Thursday, August 04, 2011 03:34:17 AM Khem Raj wrote:
> PREFERRED_VERSION_pn-u-boot = "v2011.03+git%"
Works perfect: Both 2011.03 and 2011.06 are running fine. Thanks

Re: Howto pin u-boot to a version supplied by oe-core

[Paul Eggleton]

On Thursday 04 August 2011 02:34:17 Khem Raj wrote:
> in anycase what you need to lock is PV and the recipes in oe-core has
> 
> u-boot_2011.03.bb:PV = "v2011.03+git${SRCPV}"
> u-boot_2011.06.bb:PV = "v2011.06+git${SRCPV}"
> 
> So what you need is
> 
> PREFERRED_VERSION_pn-u-boot = "v2011.03+git%"

Hmm, I wonder if the message could be changed to be more helpful for the cases 
where the recipe grabs source from some SCM. I have to admit I did not 
consider this case when writing the PREFERRED_VERSION message change.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre