Re: bits about the future with VTK in Buster

2017-04-07 Thread Anton Gladky
Hi Gert, thanks for the info and analysis! Well, to make a decision we should firstly check how many packages are not able to be built "out of box" with the new backend. Than we can decide what to do with this rest of packages. I do not like the idea to keep both versions of VTK parallely, it can

Re: bits about the future with VTK in Buster

2017-04-06 Thread Karsten Hilbert
On Thu, Apr 06, 2017 at 11:27:48AM +0200, Gert Wollny wrote: > > I wonder whether we could keep VTK-6 for projects using the old API > > and force VTK-7-only projects to use the new one? VTK-6 and VTK-7 > > should be co-installable, right? > > I think the language bindings are not co-installable,

Re: bits about the future with VTK in Buster

2017-04-06 Thread Gert Wollny
> I wonder whether we could keep VTK-6 for projects using the old API > and force VTK-7-only projects to use the new one? VTK-6 and VTK-7 > should be co-installable, right? > I think the language bindings are not co-installable, but those could be dropped from the VTK-6 package. -Gert

Re: bits about the future with VTK in Buster

2017-04-06 Thread Ghislain Vaillant
On Thu, 2017-04-06 at 10:27 +0200, Gert Wollny wrote: > Hello all, > > I just drop this here for future reference. Thanks for looking into it and summarizing your findings. > I've experimented a bit with VTK-7.1 and among other, minor issues I > came across the problem that VTK now defaults to

bits about the future with VTK in Buster

2017-04-06 Thread Gert Wollny
Hello all, I just drop this here for future reference. I've experimented a bit with VTK-7.1 and among other, minor issues I came across the problem that VTK now defaults to,  and, hence, encourages the use of, a new renderer backend, called OpenGL2 that requires an OpenGL 3.2 context. The old