Re: Skip VTK7 and go directly VTK8? Was: Re: vtk6 and vtk7
Christophe TROPHIME
Research Engineer
CNRS - LNCMI
25, rue des Martyrs
BP 166
38042 GRENOBLE Cedex 9
FRANCE
Tel : +33 (0)4 76 88 90 02
Fax : +33 (0) 4 76 88 10 01
Office U 19
M@il : christophe.trophime@lncmi.cnrs.fr
----- Original Message -----
> From: "Gert Wollny" <gw.fossdev@gmail.com>
> To: "Christophe Trophime" <christophe.trophime@lncmi.cnrs.fr>, "Ghislain Vaillant" <ghisvail@gmail.com>
> Cc: "Nico Schlömer" <nico.schloemer@gmail.com>, dparsons@debian.org, "Debian Science List"
> <debian-science@lists.debian.org>
> Sent: Sunday, November 26, 2017 2:27:22 PM
> Subject: Re: Skip VTK7 and go directly VTK8? Was: Re: vtk6 and vtk7
>
> Am Sonntag, den 26.11.2017, 09:55 +0100 schrieb Christophe Trophime:
> >
> >
> > Providing very few changes to paraview package any package using VTK
> > can be built on top of ParaView.
>
> I guess this version of VTK included in paraview is build with the
> OpenGL2 render backend, right? In that case it will not suffice for
> all packages, because some need the soon-to-be-droppped OpenGL render
> interface, i.e. dor that reason a part of vtk6 will probably have to
> be kept, although probably only the library and dev package.
>
> >
> > Sorry to jump into this discussion but I really think that some work
> > is needed for ParaView/VTK, at least to clarify the question of VTK
> > version?
> My concern is mostly about keeping some applications in Debian that are
> of interest to debian.med, and will currently not run with newer
> versions of VTK, mostly because of the new OPENGL2 requirements (i.e.
> OpenGL >= 3.2 and mesa not providing a compatibility context for this
> and newer versions).
>
The question of the backend could also be solved if we are able to have
multiple versions of VTK or/and Paraview side by side.
The real difficulty here is, to my knowledge, the python bindings...
since VTK or ParaView execs, libs may be appended with a version..
Just a comment about your concerns about some apps in Debian/med
we may have the same problems with hdf5 for instance. Switching to
the newest version may not always be a solution as it breaks other
packages.
The point here is that updating the package should not be "automatic"...
for such strategic libs. I would be interested in knowing how much
libs are really critical for Debian/med or Debian/science. Of course
it depends on your field but we may be able to list these apps? using popcon?
> Outside of this context I really have currently not much use for VTK,
> and specifically paraview.
>
> One concern of providing VTK via paraview could be that RC bugs in
> paraview that are unrelated to VTK would then affect more packages.
>
> Best,
> Gert
>
>
Reply to: