From: Richard Purdie <rpurdie@linux.intel.com>
To: Joshua Lock <josh@openedhand.com>
Cc: poky@yoctoproject.org
Subject: Re: BBFILE_PRIORITY confusion
Date: Mon, 22 Nov 2010 15:33:17 +0000 [thread overview]
Message-ID: <1290439997.1272.16996.camel@rex> (raw)
In-Reply-To: <1290434035.2579.15.camel@scimitar>
On Mon, 2010-11-22 at 13:53 +0000, Joshua Lock wrote:
> On Sun, 2010-11-21 at 04:13 -0700, Gary Thomas wrote:
> >
> > It seems to me that BBFILE_PRIORITY is a bit too zealous; barring any other
> > constraint, I should think that the 2.6.32 recipe should always take precedence.
> >
> > Am I missing something here, or is it a bug?
> >
>
> This is working exactly as intended, you've told bitbake that the
> manufacturer layer has a higher priority so it's using that to satisfy
> any recipe it can, regardless of version. If you'd like the platform to
> be able to be prioritised over the manufacturer you'd need to adjust the
> priority accordingly.
>
> If you want the most highest version recipe to be used, regardless of
> layer, you could set the priorities to be the same.
>
> Perhaps you could work around this by having your platforms pin specific
> kernel versions when they need an older kernel?
Or you give the layers the same priority, then the usual mechanisms take
effect. As Joshua says, its doing exactly what its intended to do
though.
Cheers,
Richard
next prev parent reply other threads:[~2010-11-22 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 11:13 BBFILE_PRIORITY confusion Gary Thomas
2010-11-22 13:53 ` Joshua Lock
2010-11-22 15:33 ` Richard Purdie [this message]
2010-11-22 15:37 ` Gary Thomas
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=1290439997.1272.16996.camel@rex \
--to=rpurdie@linux.intel.com \
--cc=josh@openedhand.com \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.