From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] qt4e-demo-image: Fix bug 999
Date: Tue, 23 Aug 2011 13:53:13 +0100 [thread overview]
Message-ID: <201108231353.13437.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <63FF64B9-6C5E-4C87-9DFD-7AD9A88A5DD1@dominion.thruhere.net>
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.
The purpose of having these images was to have a simple way to test that Qt
has built correctly and is functional. If Qt is in OE-core I don't think
that's unreasonable.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-08-23 12:58 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 [this message]
2011-08-23 15:10 ` Koen Kooi
2011-08-24 0:16 ` Saul Wold
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=201108231353.13437.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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