[oe] [meta-oe][dizzy]Update PyQt and related recipes

[Otavio Salvador]

On Mon, Mar 2, 2015 at 7:05 PM, Philip Balister <philip at balister.org> wrote:
> On 03/02/2015 03:56 PM, Otavio Salvador wrote:
>> On Mon, Mar 2, 2015 at 5:49 PM, Philip Balister <philip at balister.org> wrote:
>>> On 02/27/2015 04:37 PM, Otavio Salvador wrote:
>>>> On Fri, Feb 27, 2015 at 5:42 PM, Philip Balister <philip at balister.org> wrote:
>>>>> On 02/27/2015 12:31 AM, Martin Jansa 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.
>>>>>
>>>>> Basically, what is in dizzy doesn't work for anyone. To make it work, we
>>>>> need to upgrade to pickup some changes that made pyqt easier to cross
>>>>> compile.
>>>>
>>>> Yes, this is why I support this update however we need to fix the sip
>>>> upgrade path.
>>>>
>>>
>>> What's wrong with the sip update path? Originally, there was only a
>>> recipe for sip-native, this patch replaces the sip-native recipe with
>>> one that works for native and target.
>>
>> Upgrade path. python-sip died no?
>>
>
> Ah yes. python-sip was built from the sip package. The new sip recipe
> handles the building and installation of the python bits.
>
> How do we tell package manages what happened? (Yes I suck at packaging)
>
> In reality, I doubt many people installed python-sip.

Why you don't split it? I think it makes sense to have it splitted.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750