"Smith, Barry F. via petsc-dev" <[email protected]> writes:
> Yes. If the testing system were smart enough we could have the tests > actually update the "prebuilt" automatically when things change. This would > be more scalable in human efficiency. In addition when setting up a new test > machine no need to manually make the prebuilts, the testing will just build > them the first time it is run. > > Each examples/arch-* would have a variable listing the packages it uses > that it wishes to be prebuilt. Each examples/arch-* would have list a dir for > keeping its prebuilts. This could possibly be in the petsc directory. The > script would check for any missing prebuilt, then build them with --prefix. > It would then check using the version in the package.py and the version of > the prebuilt (how to get that info easily?) and rebuild any packages that > need updating with --prefix. Easy Peasy. Then run the regular tests. An alternative would be to spack install those dependencies since it handles caching and upgrades more reliably.
