Heya :-) VisIt doesn't adhere to the filesystem hierarchy standard. Here is a quick listing of what lurks beneath /opt/visit/${PV}/linux-`arch`:

```
/opt/visit/2.7.2/linux-x86_64/ultrawrapper
/opt/visit/2.7.2/linux-x86_64/resources
/opt/visit/2.7.2/linux-x86_64/resources/clients
/opt/visit/2.7.2/linux-x86_64/resources/translations
/opt/visit/2.7.2/linux-x86_64/resources/hosts
/opt/visit/2.7.2/linux-x86_64/resources/movietemplates
/opt/visit/2.7.2/linux-x86_64/resources/usage
/opt/visit/2.7.2/linux-x86_64/resources/help
/opt/visit/2.7.2/linux-x86_64/resources/colortables
/opt/visit/2.7.2/linux-x86_64/bin
/opt/visit/2.7.2/linux-x86_64/lib
/opt/visit/2.7.2/linux-x86_64/lib/site-packages
/opt/visit/2.7.2/linux-x86_64/libsim
/opt/visit/2.7.2/linux-x86_64/libsim/V1
/opt/visit/2.7.2/linux-x86_64/libsim/V2
/opt/visit/2.7.2/linux-x86_64/include
/opt/visit/2.7.2/linux-x86_64/include/visit
/opt/visit/2.7.2/linux-x86_64/plugins
/opt/visit/2.7.2/linux-x86_64/plugins/operators
/opt/visit/2.7.2/linux-x86_64/plugins/plots
/opt/visit/2.7.2/linux-x86_64/plugins/databases
```

I'd go inside the the CMake-Scripts, but, as you can see in the current patch set, those are full of duplications, so that wouldn't be really sustainable: every new revision from upstream that adds/removes components would break the ebuild.