From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 1/1] qt4e-demo-image: Fix bug 999
Date: Tue, 23 Aug 2011 17:16:30 -0700 [thread overview]
Message-ID: <4E5442DE.7060103@linux.intel.com> (raw)
In-Reply-To: <6BCD0FB4-907F-4055-A405-F236F6D3D4AA@dominion.thruhere.net>
On 08/23/2011 08:10 AM, Koen Kooi wrote:
>
> Op 23 aug. 2011, om 14:53 heeft Paul Eggleton het volgende geschreven:
>
>> On Tuesday 23 August 2011 13:27:11 you wrote:
>>> I would lean toward a seperate meta-qt layer, not sure if it should be
>>> hosted in the oe-core git repo, meta-oe or a completely seperate git repo.
>>
>> Possibly we should have meta-qt for Qt applications and additional libraries
>> such as Qwt (and I'm all for moving our current Qt apps there, they don't
>> really belong in OE-core IMHO). If you're suggesting moving out Qt itself
>> though, I think Qt belongs in OE-core, certainly as much as GTK+ does.
>
> I still say that gtk+ should be in it's own layer as well :) I hope to have some time in september to come up with a proposal to rearrange oe-core and meta-oe in a more logical set of layers.
Yea, we should discuss this further (post 1.1) for me, while I think
it's important to have some demos/test with the oe-core (if we keep it
in oe-core), I am not sure we should have all the tests there.
I would suggest possibly renaming the current meta-qt3 to meta-qt and
including this set of demos there.
Comments?
Sau!
We already have a QT3 layer, maybe it makes sense to make that a generic
meta-qt layer and have things reside in it.
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2011-08-24 0:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 10:57 [PATCH 0/1] qt4e-demo-image: Fix bug 999 Xiaofeng Yan
2011-08-23 10:57 ` [PATCH 1/1] " Xiaofeng Yan
2011-08-23 12:18 ` Paul Eggleton
2011-08-23 12:27 ` Koen Kooi
2011-08-23 12:53 ` Paul Eggleton
2011-08-23 15:10 ` Koen Kooi
2011-08-24 0:16 ` Saul Wold [this message]
2011-08-24 1:04 ` Paul Eggleton
-- strict thread matches above, loose matches on Subject: below --
2011-08-24 6:34 [PATCH 0/1] " Xiaofeng Yan
2011-08-24 6:34 ` [PATCH 1/1] " Xiaofeng Yan
2011-08-24 23:36 ` Saul Wold
2011-08-25 0:13 ` Paul Eggleton
2011-08-25 2:10 ` Xiaofeng Yan
2011-09-05 1:47 [PATCH 0/1]:qt4e-demo-image: " Xiaofeng Yan
2011-09-05 1:47 ` [PATCH 1/1] qt4e-demo-image:Fix " Xiaofeng Yan
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=4E5442DE.7060103@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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