From: "Eric Bénard" <eric@eukrea.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Wolfgang.Hauser.external@cassidian.com
Subject: Re: Backporting qt4 to 2011.03-maintenance
Date: Fri, 16 Sep 2011 10:48:58 +0200 [thread overview]
Message-ID: <4E730D7A.7010700@eukrea.com> (raw)
In-Reply-To: <0C757E680E33864AB113392C7E83F910BE51E8@GSX300A.mxchg.m.corp>
Hi Wolfgang,
Le 16/09/2011 10:46, Hauser, Wolfgang (external) a écrit :
> is it possible to take the recipes for qt 4.7.x from oe-core and use it in
> a 2011.03-maintenance tag based OE environment ?
>
> What are the main differences, if there are one ?
>
I would recommend to update qt to 4.7.4 (git mv + checksum change) + integrate
the blacklist-diginotar-certs patch in oe-dev as qt in oe-core is not yet at
the functional level of oe-dev (broken SDK, broken translations ...).
Eric
prev parent reply other threads:[~2011-09-16 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 8:46 Backporting qt4 to 2011.03-maintenance Hauser, Wolfgang (external)
2011-09-16 8:48 ` Eric Bénard [this message]
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=4E730D7A.7010700@eukrea.com \
--to=eric@eukrea.com \
--cc=Wolfgang.Hauser.external@cassidian.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