[oe] [PATCH 6/8] python-pygobject: add a recipe

[Alexander Kanavin]

On 06/10/2016 03:33 PM, Martin Jansa wrote:
> On Tue, May 24, 2016 at 02:56:59PM +0300, Alexander Kanavin wrote:
>> oe-core provides only python3-pygobject now, and a few recipes in meta-oe
>> still need the version built against Python 2.
>
> I've merged this but now it started to fail:
>
> | checking whether python2.7 version >= 2.7... yes
> | checking for python2.7 version... 2.7
> | checking for python2.7 platform... linux2
> | checking for python2.7 script directory... ${prefix}/lib64/python2.7/site-packages
> | checking for python2.7 extension module directory... ${exec_prefix}/lib64/python2.7/site-packages
> | checking for python version... (cached) 2.7
> | checking for python platform... (cached) linux2
> | checking for python script directory... (cached) ${prefix}/lib64/python2.7/site-packages
> | checking for python extension module directory... (cached) ${exec_prefix}/lib64/python2.7/site-packages
> | checking for headers required to compile python extensions... not found
> | configure: error: Python headers not found
> | WARNING: python-pygobject/3.18.2-r0/temp/run.do_configure.32140:1 exit 1 from 'exit 1'
> | ERROR: Function failed: do_configure (log file is located at python-pygobject/3.18.2-r0/temp/log.do_configure.32140)
> NOTE: recipe python-pygobject-3.18.2-r0: task do_configure: Failed

I think the recipe can be dropped with its dependencies:
- python-dbusmock is not used by anything
- python-cloudeebus is not used by anything
- bluez4 testtools have been superseded by test tools from bluez5 and 
can be disabled

Alex