On Oct 29, 2013, at 1:51 PM, Jed Brown <[email protected]> wrote:
> Barry Smith <[email protected]> writes: >> Or simpler just have the —with-clean nuke external packages; makes >> life easy. By "store the tarballs in a common place” and SHA1 crap >> you are making the system more complicated to understand and >> maintain. > > People will complain when they have to download the same tarball many > times. But I don't especially care as long as the builds are done > inside $PETSC_ARCH instead of in a common place. (This is also useful > when building multiple configurations of PETSc in parallel.) Besides us, hardly anyone uses more than 2 PETSC_ARCH! So how about just moving externalpackages into $PETSC_ARCH and don’t build some elaborate scheme that reuses tar balls for a tiny number of people. In other words a clean truly means clean and gets new tar balls. Barry
