> > BTW: externalpackages/package/PETSC_ARCH is more like a default prefix > for the package. Ideally if the package supported prefix - we would > use it and put the stuff directly in PETSC_DIR/PETSC_ARCH - and > externalpackages/package/PETSC_ARCH won't have any stuff in it. >
Ah, ok, that makes sense now. > Perhaps some package.py files are doing things manually and using > externalpackages/package/PETSC_ARCH as temporary location - and later > coping things over to PETSC_DIR/PETSC_ARCH - and not cleaning things > up. [in externalpackages/package/PETSC_ARCH]. Right, but what should we do about it? It could potentially cause a bunch of headaches. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120224/ff6ba6f9/attachment.html>
