Bug#654839: Fwd: [Paraview] Convenient copy of VTK within ParaView

Mathieu Malaterre mathieu.malaterre at gmail.com
Mon Jan 16 09:08:09 UTC 2012


On Sun, Jan 15, 2012 at 8:21 PM, Steve M. Robbins <steve at sumost.ca> wrote:
> On Sun, Jan 15, 2012 at 11:22:33AM +0100, Mathieu Malaterre wrote:
>> Forwarding upstream comments.
>> I think now we have two options:
>>
>> - Start working on PV 3.12 and getting rid of convenient copy of VTK.
>> I do not think it will be too difficult since VTK 5.8.0 was released
>> not too long ago
>> - Mark that PV 3.12 is shipped with convenient copy of VTK, and only
>> upload without convenient VTK when upstream make the first move...
>
> I would suggest the second option.  As upstream says "its fraught with
> complications" until they sync releases.  The "complications" will
> translate into either extra work for Debian packagers or extra bugs
> for Debian users.  Or both.  I don't see any good reason to deal with
> complications.  The usual arguments about security are easily
> dispatched: how many security fixes has Debian applied to VTK
> (independently of upstream) in the last 5 years?

That makes sense. Now what should be done with paraview-python, in
theory it should not possibly conflict with vtk.


-- 
Mathieu





More information about the debian-science-maintainers mailing list