From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/10] qt4: upgrade to 4.8.3 and cleanup
Date: Thu, 27 Sep 2012 17:45:30 +0200 [thread overview]
Message-ID: <20120927154530.GE3454@jama.jama.net> (raw)
In-Reply-To: <2523654.gPkJCTUPfL@helios>
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
On Thu, Sep 27, 2012 at 04:10:20PM +0100, Paul Eggleton wrote:
> On Thursday 27 September 2012 00:27:05 Martin Jansa wrote:
> > Please test on more architectures.
> > I've tested complete qt4-native + qt4-free-x11 on armv4t.
> > And only do_patch for nativesdk-qt4-tools, qt-mobility-*, qt4-embedded.
>
> So this is great work and these patches look good, although I'm still not
> particularly happy with breaking out so many of the configure options because
> I'm convinced it won't stop here; but it's possible I might be overruled on
> this issue.
I've added that, because meta-webos layer disables more stuff then .inc
file forces enabled, so I would have to rewrite whole QT_CONFIG_FLAGS
(if I don't want to have e.g. -webkit from .inc and -no-webkit appended
after that through QT_DISTRO_FLAGS).
But it can be just 2 variables instead of 6 if it's issue.
> The bigger problem is when these patches are arriving - we're late into the
> stabilisation period and given the choice I'd prefer not to merge them until
> the next development cycle.
The cleanup part is formal only, so with low risk IMHO.
I have some layer with .bbappends to it which needs 4.8.3 (or 4.8.2) so recipe
even with negative D_P would help me to be able to use next oe-core release.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-09-27 15:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 22:27 [PATCH 00/10] qt4: upgrade to 4.8.3 and cleanup Martin Jansa
2012-09-26 22:27 ` [PATCH 01/10] qt4-tools-nativesdk.inc: rename to nativesdk-qt4-tools.inc Martin Jansa
2012-09-26 22:27 ` [PATCH 02/10] qt4: use releases.qt-project.org instead of get.qt.nokia.com Martin Jansa
2012-09-26 22:27 ` [PATCH 03/10] qt4: rename qt-4.8.1 to qt4-4.8.1 to match other .inc and .bb Martin Jansa
2012-09-26 22:27 ` [PATCH 04/10] qt4.inc: move more options to separate variables Martin Jansa
2012-09-26 22:27 ` [PATCH 05/10] qt-mobility: move qt-mobility patches to separate dir Martin Jansa
2012-09-26 22:27 ` [PATCH 06/10] qt4: move patches from files to qt4-4.8.1 Martin Jansa
2012-09-26 22:27 ` [PATCH 07/10] qt4: drop patches not used in any recipe Martin Jansa
2012-09-26 22:27 ` [PATCH 08/10] qt4: replace all local patches with git patches with headers Martin Jansa
2012-09-26 22:27 ` [PATCH 09/10] qt4: PR bumps Martin Jansa
2012-09-26 22:27 ` [PATCH 10/10] qt4: upgrade to 4.8.3 Martin Jansa
[not found] ` <cover.1349134104.git.Martin.Jansa@gmail.com>
2012-10-01 23:28 ` [PATCHv2 10/10] qt4: add 4.8.3 version with negative D_P Martin Jansa
2012-09-27 15:10 ` [PATCH 00/10] qt4: upgrade to 4.8.3 and cleanup Paul Eggleton
2012-09-27 15:45 ` Martin Jansa [this message]
2012-09-28 6:37 ` Anders Darander
2012-09-28 16:43 ` Martin Jansa
2012-09-30 20:18 ` Martin Jansa
2012-10-01 14:31 ` Martin Jansa
2012-10-01 23:26 ` Martin Jansa
2012-10-02 8:29 ` Martin Jansa
2012-10-03 1:40 ` Saul Wold
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=20120927154530.GE3454@jama.jama.net \
--to=martin.jansa@gmail.com \
--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