[petsc-dev] builds of PETSc based packages should not get their own secret files

[Barry Smith]

  For packages that are built after PETSc configure (and or install is done) slepc, hpddm etc we've traditional saved the output  in its own file stashed away somewhere. 

  For the CI this is driving me nuts because when they fail the output is essentially "lost" and thus it is impossible to determine what has gone wrong. 

  I have started to directly output in the same stream as the PETSc compiles to make debugging much easier. Generally the packages are relatively small and don't have a huge amount of output when compiling correctly.  I did it for PETSc4py and SLEPc (slepc4py is a mystery yet how it get's hidden in slepc). 

  Are there any large downsides to this plan?

  Barry