Part of the trouble is that VTK_USE_EXTERNAL option is not fully supported right now by upstream. However we can build paraview on top of vtk (see branch use_external_vtk in paraview.git)
There may be a way to install vtk 6.xx libs from paraview that won't clash with any vtk package except python-vtk. From my trials it seems that to get a working paraview-python we must ship a python-vtk package. I can create a new branch on paraview.git to see my progress in that direction if you wish.... Christophe TROPHIME Research Engineer CNRS - LNCMI 25, rue des Martyrs BP 166 38042 GRENOBLE Cedex 9 FRANCE Tel : +33 (0)4 76 88 90 02 Fax : +33 (0) 4 76 88 10 01 Office U 19 M@il : christophe.troph...@lncmi.cnrs.fr ----- Mail original ----- De: "Anton Gladky" <gl...@debian.org> À: "Dominique Belhachemi" <domi...@debian.org>, "Christophe Trophime" <christophe.troph...@lncmi.cnrs.fr> Cc: "Mathieu Malaterre" <ma...@debian.org>, "732362" <732...@bugs.debian.org> Envoyé: Mardi 17 Décembre 2013 14:39:45 Objet: Re: Bug#732362: vtk 5.10.1 for jessie 2013/12/17 Dominique Belhachemi <domi...@debian.org>: > Anton, we might need your help with the paraview package. We need to figure > out a way to build against system VTK libraries. This would help avoiding > file conflicts and the vtk package would get a better test coverage. Christophe Trophime has done already a job to escape such conflicts. Moreover he proposed to build vtk-binaries from Paraview-source. Looks reasonable... Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
