I think we’re basically saying the same thing - as a start, I have a repo for avogenerators - that can and should be downloaded in the superbuild. (I’ll create one for file formats and workflows shortly.)
I agree 100% that the default version should install with the latest set of scripts at the time of release. I was asking for help with the CMake syntax to download the repo, so I can remove the duplicated scripts currently in
My comment was that by having the scripts in separate repos (rather than living in
avogadrolibs) then users who want to install newer versions (e.g., use the downloader feature) can do so. That feature should be optional (e.g., users who can’t access the network).
I already have code to load Python scripts - as you said, the local version overrides the installed version. The code actually checks the individual menu paths for each script - this way if ORCA or GAMESS or Q-Chem create separate plugins, that could be installed locally and replace the default scripts.
- I want to see the superbuild use CMake to grab scripts from a separate repo
- I’m not quite sure how to do that myself
- Plugin downloads and/or updates will always be optional