[Debian-med-packaging] Bug#571491:

[Mathieu Malaterre]

reassign 571491  vtk
thanks

Ok here is the summary.

In order to build the VTK-GDCM extension, GDCM needs a pre-installed
copy of VTK on the target machine. In this case a VTK 5.4 compiled
against python2.5 was found.

When building the VTK-GDCM extension, GDCM does not do anything bug
simply passing the exact same compilation flags (thanks to cmake) from
VTK to the VTK-GDCM extension.
In this case:

$ grep python /usr/lib/vtk-5.4/VTKConfig.cmake
SET(VTK_INCLUDE_DIRS
"${VTK_INSTALL_PREFIX}/include/vtk-5.4;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/lib/openmpi/include;/usr/lib/openmpi/include/openmpi;/usr/include/tcl8.5;/usr/include/python2.5;/usr/include/tcl8.5;/usr/lib/jvm/default-java/include;/usr/lib/jvm/default-java/include;/usr/lib/jvm/default-java/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include;/usr/include/libxml2;/usr/include;/usr/include/freetype2")
SET(VTK_PYTHONPATH_DIRS
"/usr/lib/python2.5/site-packages;/usr/lib/python2.5/site-packages")


So VTK-GDCM is only an extension of VTK. Thus whenever VTK will
compile with python2.6, VTK-GDCM should compile just fine (the
previous errors was reported against a VTK header).

Reassigning to VTK package.