Ok, do you know which plugins you would like to add support for?
http://www.paraview.org/Wiki/VisIt_Database_Bridge#Building_ParaView
mentions that you only need boost to add support for visitbridge
but silo, cgns and mili each need an external library which is not in the main repos so I will to bring in those if you want them.

So, I can enable visitbridge, but which external libs would you like support for?

I worked with CGNS. This is quite popular format. I don't insist on including this reader to package, but I noticed that CGNS format is supported in windows binary version, but not in archlinux version.
I would be happy if you add at least cgns reader to package, but this means building cgns library too, and including it to "community" as dependency. This is not good idea, in my opinion. However, I'm maintainer of "libcgns" package in AUR.

So, I'm going to read more about adding new readers for visitbridge. May be this procedure doesn't require rebuilding paraview.

Looks like all of the readers listed under
http://www.paraview.org/Wiki/VisIt_Database_Bridge#Which_of_VisIt.27s_databases_are_available.3F
get enabled with PARAVIEW_USE_VISITBRIDGE except cgns, silo, and mili which require external libs.

Please let me know what you come up with, but I think that it does require a rebuild of paraview in order to support these readers.

Yes, you are right. It's a pitty, but support cgns, silo and milo readers reqiures a rebuild of paraview.
I want support of cgns format and I'm going to add a package in AUR with libcgns as dependency. But if you wish, you can maintain this package ( I can help if you don't want to waste your time: so you can send to me your PKGBUILD for paraview, I will edit and send it back to you).

ok, I plan on doing the following:

1.) bring libcgns into [community]
2.) add PARAVIEW_USE_VISITBRIDGE=ON to the paraview PKGBUILD
2.) enable support for cgns in paraview by adding VISIT_BUILD_READER_CGNS=ON to the paraview PKGBUILD

Does this look good to you? Can I bring in libcgns into community, since that's the only way I can enable the reader.

actually, I forgot that I can't rebuild paraview since boost was disabled in this current version in [community] because of an old vtk bug with boost.

A new paraview version is available which I think compiles with the latest boost version, but I can't build it because of another bug with compiling against protobuf: http://paraview.org/Bug/view.php?id=12718

So until I can compile the latest version of paraview (3.12.0), I can't do anything about this.

Yes, you can bring libcgns into community.

So, lets wait until the bug is fixed.

brought in libcgns, figuring out the rest.

edit: this is the bug that's holding me back http://paraview.org/Bug/view.php?id=12718 although I think I might have figured it out

So after fixing (or working around rather) http://paraview.org/Bug/view.php?id=12718 I enabled PARAVIEW_USE_VISITBRIDGE and rebuilt.
This time, I got another error which I opened another bug report for: http://paraview.org/Bug/view.php?id=12849
At least I got paraview updated to 3.12.0 as a result and brought in libcgns to community.

Had to create libcgns2 since paraview uses visit which doesn't support libcgns 3.
rebuilt paraview and it should soon be in community.
Thanks for your feature request, and if you have any more, please open reports for those also.