Add multi-repository support to Trilinos for inserted packages
Created by: bartlettroscoe
Next Action Status:
Configure of MOOCHO, Mesquite, etc. fail due to wrong base directory. Next: Debug configure problems when running under CTest driver script.
Blocked By: #158 (closed)
Relates To: SEMS JIRA Issue TRIL-50, #440, #452
CC: @bmpersc, @jwillenbring
Description:
As part of the effort to trim down the Trilinos git repo as part of the move to GitHub, several Trilinos packages (MOOCHO, CTrilinos, ForTrilinos, Sundance, Mesquite, etc.) were filtered out of the main Trilinos git repo and were given their own GitHub repos. The plan for adding them back into the automated builds is documented in the Google Doc Proposal for trimming down Trilinos repo.
Note that all of the support for managing multiple repos already exists in TriBITS and has been used for CASL VERA development for many years. For an overview, see "Multi-Repository Support".
Definition of Done:
All Trilinos packages that were pulled out but still plan to be tested and released are back running under automated testing and will be automatically included in future releases (using clone_extra_repos.py
and gitdist
).
Tasks:
- Add Trilinos packages back as "Inserted Packages" (This is so that they will be defined as TriBITS packages in a way that does not interfere with other "Extra Packages" in "Extra Repos", e.g. through
-DTrilinos_EXTRA_REPOSITORIES=<repo0>,<repo1>,...
). See below [Done] - Add wiki page to Trilinos GitHub wiki site describing the handling of extra repos (e.g.
clone_extra-repos.py
,gitdist
, etc.)