Bug#637397: Possible solutions

[Mathieu Malaterre]

On Mon, Aug 29, 2011 at 4:35 AM, Steve M. Robbins <steve at sumost.ca> wrote:
> I think the rest of this thread got off onto a tangent.  In my mind,
> the germane question is not why Paraview embeds a patched VTK source
> tree but, rather: why is the paraview binary package now installing
> the VTK tools like vtkWrapPython?

Indeed, that's the actual issue. Thanks Steve.

> Why does a running paraview binary need vtkWrapPython?

That was also my initial question.

> Can it be stuck into /usr/lib/paraview to avoid the conflict?

I believe the only outstanding issue is that VTK 5.8 is not released
yet. Therefore vtkWrapPython* tools from ParaView 3.10 are much more
advanced (more options) than that of VTK 5.6.

So maybe putting those into a paraview namespace will solve all those
issues: if one user needs to wrap VTK 5.6 class, they will use
vtkWrapPython from vtk package, if the vtkWrapPython* are missing
newer option, they could use a paraview-python-dev package which
provide the latest and greatest of paraview-vtk-python dev tools...

2cts
-- 
Mathieu