vtk: switch to vtk_9

[veprbl]

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 22.11 Release Notes (or backporting 22.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[veprbl]

@GrahamcOfBorg eval

[bcdarwin]

It seems libX11 and libGL should be propagated from vtk_9 since in my experiments, any package depending on vtk_9 (but not vtk_8) without these inputs will fail during cmakeConfigurePhase. (f3d being a typical example.)

[veprbl]

@bcdarwin Thanks for the tip!

[wegank]

@ofborg eval

[wegank]

@veprbl Is this PR good to merge? Got #203386 using vtk_9 with Python support here.

[veprbl]

Needs more work. Minimal option is to pin all the broken software to vtk_8.

[wegank]

Needs more work. Minimal option is to pin all the broken software to vtk_8.

Done in #212455.