From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [Patch v3] gconf: enable gtk+ 2.0 support to build gconf-sanity-check-2
Date: Tue, 17 Jan 2012 10:19:53 -0800 [thread overview]
Message-ID: <4F15BBC9.2030707@linux.intel.com> (raw)
In-Reply-To: <4F15A22B.6060004@balister.org>
On 17/01/12 08:30, Philip Balister wrote:
> On 01/16/2012 01:45 PM, Phil Blundell wrote:
>> On Mon, 2012-01-16 at 10:19 -0800, Steve Sakoman wrote:
>>> My tested-by was indeed performed with the meta-oe layer enabled.
>>>
>>> In the future I will make clear what layers were used in my testing.
>>>
>>> I fear that this kind of thing is going to bite us repeatedly :-(
>>
>> It's never been entirely clear to me why meta-oe needs to override quite
>> so many bits of oe-core as it does. I think you're probably right that,
>> as long as it continues to do so, and people enable meta-oe during
>> testing, this sort of issue probably is going to continue to occur.
>
> It sounds like we need to collect a list of bits of oe-core that meta-oe
> overrides and work out a plan to resolve these differences.
Agreed! There have been a couple of efforts for specific recipes, most
recently udev work from Otavio.
I'd definitely like to see the differences resolved, or at least
reduced, and will be happy to help work through some of the issues.
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-17 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 19:17 [Patch v3] gconf: enable gtk+ 2.0 support to build gconf-sanity-check-2 Koen Kooi
2012-01-16 14:07 ` Steve Sakoman
2012-01-16 14:12 ` Richard Purdie
2012-01-16 18:06 ` Richard Purdie
2012-01-16 18:19 ` Steve Sakoman
2012-01-16 18:45 ` Phil Blundell
2012-01-17 16:30 ` Philip Balister
2012-01-17 18:19 ` Joshua Lock [this message]
2012-01-22 2:39 ` Khem Raj
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=4F15BBC9.2030707@linux.intel.com \
--to=josh@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox