[Paraview-developers] On user submodule status

[Utkarsh Ayachit]

John,

> Option 3: I had imagined that I have a public git repo, kitware clones it locally in the 'User contributed plugins' section of your git space. Inside the paraview Tree, the git clone is a submodule much like Xdmf or IceT, and When a new version is available, I go through the process of submitting a patch to paraview with the correct submodule sha. This gets included in the next version.

There's pretty much no difference between this and the current
approach expect that your plugin will be a submodule rather than a
sub-dir. I was under the impression that you didnt want "us" to touch
the code when it needed to be updated after any API changes, and for
that to happen we have to take the plugin out of the ParaView source.

I think the superbuild option is the best, if you agree. Documentation
on that will be made available soon. I am in  the processes of
updating the PAraVIew CMakeLists to fix the install rules, among other
things and after that we'll move on to cleaning up the superbuilds and
make them official.

Utkarsh