For vtkDICOM, if I was forced to choose between supporting external builds vs. building as a remote module, then I would definitely go for external build. However, I can’t deny that I like the convenience of remote modules and don’t want them to go away.
One concern that I have is packaging (pypi). Are the remote modules going to be included in the main vtk package? I kinda think they shouldn’t, even though it means I’ll have to make my own vtkDICOM pypi package. Neither does it make sense for them to be built by default, except for by the dashboards for testing.
Also, for Python, I don’t know if the package structure is resolved yet. The python modules for external packages obviously cannot accessed by “import vtk.<module>” or “import vtkmodules.<module>”. So should things be set up to that people use “import vtk<package_name>.<module>” or simply "import vtk<module>"?