Hello, I removed the vtk7 dependency but I needed a bunch of -dev packages.
+ libavcodec-dev, + libavformat-dev, libdouble-conversion-dev, libfftw3-dev, + libfreetype-dev, + libgdal-dev, libgdcm-tools, + libgl2ps-dev, + libglew-dev, libinsighttoolkit4-dev, liblz4-dev, + libogg-dev, libopengl-dev, + libopenmpi-dev, libqt5opengl5-dev, libqt5svg5-dev, + libswscale-dev, + libtheora-dev, libutfcpp-dev, - libvtk7-dev, libvtkgdcm-cil, libvtkgdcm-dev, libvtkgdcm-java, @@ -26,10 +37,9 @@ Build-Depends: qtbase5-dev, qttools5-dev, qtxmlpatterns5-dev-tools, - vtk7, paraview seems to use an internal version of vtk. So when I build an extension with paraview-dev, I expect to have all the -dev pulled via this package. Package: paraview-dev Version: 5.10.1-1 Priority: optional Section: libdevel Source: paraview Maintainer: Debian Science Team <[email protected]> Installed-Size: 117 MB Depends: qttools5-dev-tools, libc6 (>= 2.14), paraview (= 5.10.1-1), python3:any | python3-minimal:any, libeigen3-dev I am wondering if the right solution is not to add all these vtk dependency in the paraview -dev package ? cheers Fred -- debian-science-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
