| Summary: | sci-visualisation/paraview bundles an internal copy of sci-libs/vtk | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
| Component: | Current packages | Assignee: | Matthias Maier <tamiko> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | arne_bab, cbm, dschridde+gentoobugs, esigra, lssndrbarbieri, markusle, sam, waebbl-gentoo |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=793221 https://bugs.gentoo.org/show_bug.cgi?id=889340 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 251464, 322191 | ||
|
Description
Diego Elio Pettenò (RETIRED)
2009-01-05 18:07:05 UTC
I think this is non-trivial: http://www.paraview.org/pipermail/paraview/2008-June/008194.html Would be very cool though! Very non-trivial indeed :) However, if somebody has any pointers of how this could be achieved please let me know. cheers, Markus With the current version ParaView-3.98.1 it appears impossible to fix as the internal bundled VTK appears to be some unknown pre-release version internally labelled as 6.0.0, while as the latest available vtk release is 5.10.1. % cat ParaView-3.98.1-source/VTK/CMake/vtkVersion.cmake # VTK version number components. set(VTK_MAJOR_VERSION 6) set(VTK_MINOR_VERSION 0) set(VTK_BUILD_VERSION 0) % Paraview and VTK are one upstream and I don't expect them to have no good reason for bundling. In fact, they use TWO repositories. One for the vanilla VTK and one vor ParaviewVTK, check: http://paraview.org/gitweb?p=PVVTK.git http://vtk.org/gitweb?p=VTK.git If there are any bugs, security issues etc they fix them in both repositories anyway. so this bug will either be left open forever or get closed as wontfix I checked a few days ago... both repos seem 100% the same. But I guess it will be a major pain to unf*ck the build system so that it picks the system vtk. And actually... not very high priority to me, since it's the same upstream. *** Bug 505872 has been marked as a duplicate of this bug. *** The overcomplex CMake build system, that paraview uses, would have to be rewritten almost entirely in order to support an external vtk copy. :-/ We will not fix that in the foreseeable future. :-( It looks like PARAVIEW_USE_EXTERNAL_VTK exists now? The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4342b5087bd84cbe64de318c152b5425ec7f8d7b commit 4342b5087bd84cbe64de318c152b5425ec7f8d7b Author: Sam James <sam@gentoo.org> AuthorDate: 2021-06-02 01:23:23 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-06-02 01:23:23 +0000 sci-libs/vtk: delete README from bundled vtkm for now Avoids collision with paraview. We'll ideally try to get paraview building with system VTK again but VTK takes a while to build so anything to prevent collisions for users now is important while we investigate that possibility. Bug: https://bugs.gentoo.org/253881 Bug: https://bugs.gentoo.org/793221 Signed-off-by: Sam James <sam@gentoo.org> sci-libs/vtk/vtk-9.0.1.ebuild | 5 +++++ 1 file changed, 5 insertions(+) I was working on testing paraview against an external vtk-9 and found this in ParaViewOptions.cmake: # XXX(VTK): External VTK is not yet actually supported. if (FALSE) option(PARAVIEW_USE_EXTERNAL_VTK "Use an external VTK." OFF) mark_as_advanced(PARAVIEW_USE_EXTERNAL_VTK) else () set(PARAVIEW_USE_EXTERNAL_VTK OFF) endif () So it seems, like we have to live for now with the hack from comment #10 |
