Bug#637397: Possible solutions

[Mathieu Malaterre]

On Sat, Aug 27, 2011 at 12:35 PM, Sylvestre Ledru <sylvestre at debian.org> wrote:
> Le samedi 27 août 2011 à 13:31 +0300, Anton Gladky a écrit :
>> I see only 2 opportunities to fix it:
>>   1) Disable python-support in paraview;
>>   2) Claim, that paraview conflicts with python-vtk;
> 3) get in touch with upstream and ask them to consider changing the name
> of the binary.

paraview-python is clearly in violation with §4.13

http://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles

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:

http://anonscm.debian.org/gitweb/?p=debian-science/packages/paraview.git;a=blob;f=debian/paraview-python.install;h=8eacd2f050f81c46a1657e75879af9681b67ee22;hb=HEAD

I still do not understand why this is done ? Why would one duplicate
vtk tools from unknown vtk release dates in a paraview package ?
Anton, could you please describe your intention in doing so ? The
current paraview maintainer (Dave P.), has assured that from now on,
paraview can be built with VTK release (*).

I still believe that it would be a much better investement to start
working on paraview build process to build using an system installed
VTK.

2cts
-- 
Mathieu
(*) VTK 5.8 is still -unfortunately- not ready