On Mon, Sep 24, 2018 at 02:49:37PM +0200, Emmanuel Promayon wrote:
> - if there is no (easy) way to go back to vtk6 in gdcm (or to support both
> vtk6 and vtk7), does this means that we (upstream) need to update CamiTK to
> be based on VTK7 in order to fix this bug?
Disclaimer: I have no idea about VTK and all its dependencies.
I have read that upstream is joining Debian Science to package recent
upstream version VTK8. I expect that VTK6 will be removed from Debian
soon. So yes, I'd strongly recommend to follow the stable release cycle
of VTK upstream, which means that porting camitk to VTK7 is necessary
for including camitk into Debian and it is sensible to do some checks
with VTK8 since at some point in time this will be used in Debian. We
will not be able to support more than two VTK versions in Debian (most
probably only one).
So far for a short note - more details from VTK maintainers ...
Kind regards
Andreas.
--
http://fam-tille.de
