Bug#743177: libvtk6 should conflicts with libvtk5.8

[Mathieu Malaterre]

On 4/1/14, Anton Gladky <gladk at debian.org> wrote:
> 2014-03-31 10:58 GMT+02:00 Mathieu Malaterre <malat at debian.org>:
>
>> Typical scenarios that should not happen is an app linked against
>> vtkCommon and vtkCommonCore. This gets even worst with python
>>
>> $ python
>> import vtkCommon
>> import vtkCommonCore
>>
>
> We can declare as conflicting python-vtk and python-vtk6.
> IMHO we get a lot of troubles, declaring libvtk5.8 and libvtk6 as
> conflicting.

Hum, actually you are right. As long as libvtk5-dev and libvtk6-dev
conflicts it will be very hard for an app to link to both libvtk5.8
and libvtk6.0.

-- 
Mathieu