From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: native preferences
Date: Mon, 26 Jul 2010 10:14:45 -0700 [thread overview]
Message-ID: <4C4DC285.3070201@mentor.com> (raw)
In-Reply-To: <4C4D862E.2050202@kernelconcepts.de>
Florian Boor wrote:
> Hi,
>
> Dr. Michael Lauer schrieb:
>> Of course the preferred way - rather than switching distros - is to fix this obvious bug
>> in the OE metadata.
>
> yes I see it like this. Switching to a distribution that pins more versions is
> not really what I would call a fix. It is a workaround but should not become the
> default way to deal with such issues in OE.
> What we introduced here is clearly a bug in OE and not the distributions fault.
Except that it's a bitbake issue, not a metadata issue, iirc (which is
why it's fixed in the 1.10 branch, but not 1.8).
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-07-26 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 9:42 native preferences Florian Boor
2010-07-26 11:32 ` Koen Kooi
2010-07-26 12:08 ` Frans Meulenbroeks
2010-07-26 12:22 ` Koen Kooi
2010-07-26 12:38 ` Dr. Michael Lauer
2010-07-26 12:57 ` Florian Boor
2010-07-26 17:14 ` Tom Rini [this message]
2010-07-26 18:38 ` Koen Kooi
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=4C4DC285.3070201@mentor.com \
--to=tom_rini@mentor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox