Fix: Apply the attached patch. This adds an option configuration which controls installation of the Python bindings. When this option is selected, Python dependency is explicitly registered to the package database and the binding modules are installed. Python2.* is installed if not yet. This choice causes conflict with python3* during build. When this option is deselected, the binding modules are not installed even if any version of Python is installed. This is chosen as the default in order to keep the current default of package dependencies. Patch attached with submission follows: How-To-Repeat: CASE 1: # pkg_info -I python\* # cd /usr/ports/graphics/vigra/ # make Then the build succeeds without creating Python bindings. CASE 2: # pkg_info -I python\* python27-2.7.3_3 An interpreted object-oriented programming language # cd /usr/ports/graphics/vigra/ # make Then the build succeeds with creating Python bindings. CASE 3: # pkg_info -I python\* python27-2.7.3_3 An interpreted object-oriented programming language python32-3.2.3_1 An interpreted object-oriented programming language # cd /usr/ports/graphics/vigra/ # make Then the build will fail. This failure is also reproduced with python31-*. CASE 4: # pkg_info -I python\* python32-3.2.3_1 An interpreted object-oriented programming language # cd /usr/ports/graphics/vigra/ # make Then the build will fail. This failure is also reproduced with python31-*.
Responsible Changed From-To: freebsd-ports-bugs->fluffy Over to maintainer (via the GNATS Auto Assign Tool)
State Changed From-To: open->closed Committed. Thanks!