[opensuse-packaging] What's the easiest way determine the version of a python3 package during build?
I've looked through python3-numpy package and the only trace of version I can find is in: /usr/lib64/python3.4/site-packages/numpy-1.9.3-py3.4.egg-info and cat /usr/lib64/python3.4/site-packages/numpy-1.9.3-py3.4.egg-info|grep Version produces two lines: Metadata-Version: 1.1 Version: 1.9.3 The one I want is at the bottom. I need to ensure that the version required by blender is the one built against due to python3 abi differences. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 20/06/2016 11:23, Dave Plater wrote:
I've looked through python3-numpy package and the only trace of version I can find is in: /usr/lib64/python3.4/site-packages/numpy-1.9.3-py3.4.egg-info and cat /usr/lib64/python3.4/site-packages/numpy-1.9.3-py3.4.egg-info|grep Version produces two lines: Metadata-Version: 1.1 Version: 1.9.3 The one I want is at the bottom. I need to ensure that the version required by blender is the one built against due to python3 abi differences. Thanks Dave P I've solved the problem by requiring python3 = %{my own py_version macro} created from %(pkg-config python3 --modversion) Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mon, 2016-06-20 at 11:51 +0200, Dave Plater wrote:
On 20/06/2016 11:23, Dave Plater wrote:
I've looked through python3-numpy package and the only trace of version I can find is in: /usr/lib64/python3.4/site-packages/numpy-1.9.3-py3.4.egg-info and cat /usr/lib64/python3.4/site-packages/numpy-1.9.3-py3.4.egg- info|grep Version produces two lines: Metadata-Version: 1.1 Version: 1.9.3 The one I want is at the bottom. I need to ensure that the version required by blender is the one built against due to python3 abi differences. Thanks Dave P I've solved the problem by requiring python3 = %{my own py_version macro} created from %(pkg-config python3 --modversion) Thanks Dave P
you could simply du, in the .spec %requires_eq python3 this will add a Requires: python3 = "version of py3 in the buildroot" Cheers, Dominique
On 21/06/2016 08:37, Dominique Leuenberger / DimStar wrote:
On Mon, 2016-06-20 at 11:51 +0200, Dave Plater wrote:
On 20/06/2016 11:23, Dave Plater wrote:
I've looked through python3-numpy package and the only trace of version I can find is in: /usr/lib64/python3.4/site-packages/numpy-1.9.3-py3.4.egg-info and cat /usr/lib64/python3.4/site-packages/numpy-1.9.3-py3.4.egg- info|grep Version produces two lines: Metadata-Version: 1.1 Version: 1.9.3 The one I want is at the bottom. I need to ensure that the version required by blender is the one built against due to python3 abi differences. Thanks Dave P I've solved the problem by requiring python3 = %{my own py_version macro} created from %(pkg-config python3 --modversion) Thanks Dave P you could simply du, in the .spec %requires_eq python3
this will add a Requires: python3 = "version of py3 in the buildroot"
Cheers, Dominique Thanks, cleaner than defining a macro at the top. Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (2)
-
Dave Plater -
Dominique Leuenberger / DimStar