All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Cc: Chris Larson <clarson@kergoth.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Layer priorities influencing default version selection
Date: Tue, 2 Aug 2011 15:21:38 +0100	[thread overview]
Message-ID: <201108021521.38404.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <CABcZAN=rG0acoqcV6s-gNvvziM0ON97BzNwtZkESu+wz7vQO-g@mail.gmail.com>

On Tuesday 02 August 2011 15:14:41 Chris Larson wrote:
> as config/class priority is
> determined by order of entries in BBLAYERS, whereas recipe priority is
> determined by layer.conf.

Is that a good thing though? At the moment I'm not convinced that it is.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



WARNING: multiple messages have this Message-ID (diff)
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Cc: Chris Larson <clarson@kergoth.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [bitbake-devel] Layer priorities influencing default version selection
Date: Tue, 2 Aug 2011 15:21:38 +0100	[thread overview]
Message-ID: <201108021521.38404.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <CABcZAN=rG0acoqcV6s-gNvvziM0ON97BzNwtZkESu+wz7vQO-g@mail.gmail.com>

On Tuesday 02 August 2011 15:14:41 Chris Larson wrote:
> as config/class priority is
> determined by order of entries in BBLAYERS, whereas recipe priority is
> determined by layer.conf.

Is that a good thing though? At the moment I'm not convinced that it is.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-08-02 14:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02 11:26 Layer priorities influencing default version selection Paul Eggleton
2011-08-02 13:45 ` [OE-core] " Richard Purdie
2011-08-02 13:45   ` Richard Purdie
2011-08-02 13:52   ` [OE-core] " Phil Blundell
2011-08-02 13:52     ` Phil Blundell
2011-08-02 14:14     ` [OE-core] " Chris Larson
2011-08-02 14:14       ` Chris Larson
2011-08-02 14:21       ` Paul Eggleton [this message]
2011-08-02 14:21         ` [bitbake-devel] " Paul Eggleton
2011-08-02 14:27         ` [OE-core] " Chris Larson
2011-08-02 14:27           ` [bitbake-devel] " Chris Larson
2011-08-02 14:51           ` [OE-core] " Paul Eggleton
2011-08-02 14:51             ` [bitbake-devel] " Paul Eggleton
2011-08-02 14:55           ` [OE-core] " Mark Hatle
2011-08-02 15:35       ` Khem Raj
2011-08-02 15:35         ` [bitbake-devel] " Khem Raj
2011-08-25 10:50         ` [OE-core] " Paul Eggleton
2011-08-25 10:50           ` [bitbake-devel] " Paul Eggleton
2011-08-25 15:56           ` [OE-core] " Khem Raj
2011-08-25 15:56             ` [bitbake-devel] " Khem Raj
2011-08-25 16:58             ` [OE-core] " Paul Eggleton
2011-08-25 16:58               ` [bitbake-devel] " Paul Eggleton
2011-08-25 21:23               ` [OE-core] " Martin Jansa
2011-08-25 21:23                 ` [bitbake-devel] " Martin Jansa

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=201108021521.38404.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=clarson@kergoth.com \
    --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 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.