All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Question about OVERRIDES precedence
Date: Thu, 14 Oct 2010 15:23:14 +0200	[thread overview]
Message-ID: <i97082$i6g$2@dough.gmane.org> (raw)
In-Reply-To: <AANLkTinfQjRpwjYYL-6+He_z3tB6wm3kcW0CSEAqFVuh@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 13-10-10 23:38, Chris Larson wrote:
> On Wed, Oct 13, 2010 at 2:30 PM, Maupin, Chase <chase.maupin@ti.com> wrote:
> 
>> That was my thought as well but I can consistently cause this issue.  I
>> have tested a quick change that seems to fix the issue by reversing the list
>> before it is used in the for loop.  My change was:
> 
> 
> From discussion on IRC, we think we should just reverse the definition of
> OVERRIDES in OE, this avoids compatibility issues associated with changing
> the implementation.

Isn't the definition covered in the bitbake docs? I'm in favour of
fixing bitbake instead working around it in OE.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMtwRCMkyGM64RGpERAhyDAJ0ZKsVJEzs2Fo8iXR7F32ijePz+lwCeMuHT
vfpaqzI6gh8aKRBwE5h1WA4=
=9m/w
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-10-14 13:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 20:29 Question about OVERRIDES precedence Maupin, Chase
2010-10-13 21:21 ` Chris Larson
2010-10-13 21:30   ` Maupin, Chase
2010-10-13 21:38     ` Chris Larson
2010-10-14 13:23       ` Koen Kooi [this message]
2010-10-14 13:59         ` Chris Larson
2010-10-14 14:38           ` Phil Blundell
2010-10-14 15:29       ` Maupin, Chase
2010-10-14 15:33         ` Chris Larson
2010-10-14 16:37           ` Maupin, Chase
2010-10-14 16:41             ` Chris Larson
2010-10-14 18:03               ` Maupin, Chase

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='i97082$i6g$2@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@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.