Date: Sat, 28 Apr 2012 09:40:10 GMT From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/167368: Python version propagation breaks USE_PYTHON= usage for dependency builds Message-ID: <201204280940.q3S9eA3n027384@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/167368; it has been noted by GNATS. From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: bug-followup@FreeBSD.org, mva@freebsd.org Cc: Subject: Re: ports/167368: Python version propagation breaks USE_PYTHON= usage for dependency builds Date: Sat, 28 Apr 2012 19:04:20 +0930 graphics/openimageio defines USE_PYTHON=2.6+ graphics/blender defines USE_PYTHON=3.2 devel/boost-python-libs defines USE_PYTHON=2.5-3.1 If I install openimageio by itself it installs the python lib into the v2.7 python dir. If I install blender bringing in openimageio as a dependency it installs into v3.2 python dir, so that could be something to sort out. My guess is the openimageio pylib would need to use the same python version as boost-python-libs. Is there a reason boost-python-libs stops at 3.1? that was just the newest version at the time? could it be 2.6+ Blender uses python pretty heavily and I am certain it needs to stay against a specific version of python, I recall changes happening to upgrade support from python 3.1 to 3.2 Either way at this point blender is the only port using openimageio and the pylib being installed into python 2.7 or 3.2 libdir or disabling python bindings doesn't effect blender's use of libOpenImageIO. I'm not sure that blender would use the python bindings in the future. I am thinking this could be solved by breaking openimageio into two ports - one for a standard lib and another for python bindings.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201204280940.q3S9eA3n027384>