All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org,
	 Armin Kuster <akuster@mvista.com>
Subject: Re: [meta-oe][dizzy]Update PyQt and related recipes
Date: Thu, 26 Mar 2015 14:39:38 -0700	[thread overview]
Message-ID: <55147C9A.7090101@balister.org> (raw)
In-Reply-To: <54FF5A1D.90907@balister.org>

On 03/10/2015 01:54 PM, Philip Balister wrote:
> On 03/10/2015 04:53 PM, akuster808 wrote:
>>
>>
>> On 02/27/2015 05:41 AM, Otavio Salvador wrote:
>>> Hello Martin,
>>>
>>> On Fri, Feb 27, 2015 at 5:31 AM, Martin Jansa <martin.jansa@gmail.com>
>>> wrote:
>>>> On Tue, Feb 24, 2015 at 04:46:48PM -0800, Philip Balister wrote:
>>>>> Please pull these three patches into meta-oe/dizzy.
>>>>>
>>>>> https://github.com/openembedded/meta-oe/pull/19
>>>>>
>>>>> These lead to a working PyQt4, which will reduce the number of
>>>>> questions
>>>>> I get about gnuradio-companion not working on dizzy.
>>>>
>>>> I'm not sure if we should do upgrades in release branch which should
>>>> receive only bug fixes, but I'll let daisy maintainers to decide.
>>>
>>> I agree with your concern but I also see the improvement
>>> (cross-compile support and like) of the new PyQt4.
>>
>> Sorry I have head down for the last two weeks.
>>
>>>
>>> At same time, I think this is not ready to be merged. Checking the
>>> code changes I think we need to:
>>>
>>> * split python-sip runtime package
>>
>> So is this split being worked on ?
> 
> Yes. I sent in patches yesterday. Thanks for checking.

The patches landed in master, I have updated the branch with the 5
commits needed to make pyqt work in dizzy here:

https://github.com/balister/meta-oe/commits/pyqt-dizzy

Philip

> 
> Philip
> 
>>
>> - armin
>>>
>>> This will fix the upgrade path.
>>>


  parent reply	other threads:[~2015-03-26 21:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25  0:46 [meta-oe][dizzy]Update PyQt and related recipes Philip Balister
2015-02-25 18:29 ` Otavio Salvador
2015-02-27  8:31 ` Martin Jansa
2015-02-27 13:41   ` Otavio Salvador
2015-03-10 20:53     ` akuster808
2015-03-10 20:54       ` Philip Balister
2015-03-18 15:21         ` akuster808
2015-03-26 21:39         ` Philip Balister [this message]
2015-02-27 20:42   ` Philip Balister
2015-02-27 21:37     ` Otavio Salvador
2015-03-02 20:49       ` Philip Balister
2015-03-02 20:56         ` Otavio Salvador
2015-03-02 22:05           ` Philip Balister
2015-03-02 22:19             ` Otavio Salvador

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=55147C9A.7090101@balister.org \
    --to=philip@balister.org \
    --cc=akuster@mvista.com \
    --cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.