As explained in details libs have different SONAME (vtkCommon !=
vtkCommonCore) however they provide the same symbols (up to the ABI
diff). This is bad (tm) !
On 4/1/14, Mathieu Malaterre mathieu.malate...@gmail.com wrote:
On 4/1/14, Steve M. Robbins st...@sumost.ca wrote:
On March 31, 2014
On 4/1/14, Steve M. Robbins st...@sumost.ca wrote:
On March 31, 2014 10:58:28 AM Mathieu Malaterre wrote:
Package: libvtk6
Clearly there is something missing here. libvtk6 can be co-installed
with libvtk5.8. VTK API (ABI too) is completely incompatible in
between those two versions.
On April 1, 2014 08:59:13 AM you wrote:
As explained in details libs have different SONAME (vtkCommon !=
vtkCommonCore) however they provide the same symbols (up to the ABI
diff). This is bad (tm) !
Sorry, what details are you referring to?
-Steve
signature.asc
Description: This is a
2014-03-31 10:58 GMT+02:00 Mathieu Malaterre ma...@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
On 4/1/14, Anton Gladky gl...@debian.org wrote:
2014-03-31 10:58 GMT+02:00 Mathieu Malaterre ma...@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
python-vtk6 and python-vtk are actually already conflicting [1]
I forgot about that.
[1]
http://anonscm.debian.org/gitweb/?p=debian-science/packages/vtk6.git;a=blob;f=debian/control;h=d8d836e1f3311c99d3564c3cfbe4856ad22b07c3;hb=HEAD#l196
Anton
2014-04-01 9:36 GMT+02:00 Mathieu Malaterre
On April 1, 2014 09:12:24 AM Anton Gladky wrote:
2014-03-31 10:58 GMT+02:00 Mathieu Malaterre ma...@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
Package: libvtk6
Clearly there is something missing here. libvtk6 can be co-installed
with libvtk5.8. VTK API (ABI too) is completely incompatible in
between those two versions.
Typical scenarios that should not happen is an app linked against
vtkCommon and vtkCommonCore. This gets even worst
Hi Mathieu,
thanks for bugreport. We should probably discuss how to
proceed with this transition. From my point of view it is
better to do as quickly as possible. Declaring 5.8 and 6.0
version is possible, but during transition time we will get
tons of removed packages. What do you think?
Anton
On March 31, 2014 10:58:28 AM Mathieu Malaterre wrote:
Package: libvtk6
Clearly there is something missing here. libvtk6 can be co-installed
with libvtk5.8. VTK API (ABI too) is completely incompatible in
between those two versions.
Clearly I'm missing something, because it is routine to
10 matches
Mail list logo
