Bug#637397: Possible solutions

[Steve M. Robbins]

On Sun, Aug 28, 2011 at 05:47:50PM +0200, Sylvestre Ledru wrote:

> > It was tolerated that paraview be build with the convenient VTK
> > library, but now the package are now installing vtk related tools
> > (tools that are already installed by VTK-* package), eg:

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?

Why does a running paraview binary need vtkWrapPython?
Can it be stuck into /usr/lib/paraview to avoid the conflict?

Cheers,
-Steve

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20110828/56afb31f/attachment.pgp>