[petsc-dev] installing external packages as shared?

[Jed Brown]

Barry Smith <bsmith at mcs.anl.gov> writes:
>   3) A simple and dependable way to install many dependencies of PETSc
>   :-) and other HPC numerical software libraries

If it's a general way to install software, then why does it depend on
PETSc?  PETSc and PETSC_ARCH are currently an integral part of the way
this is distributed, but would the role you envision make sense if PETSc
was not the center of the universe?

Why can't one add packages (especially those that can be --download'ed,
but on which PETSc does not depend) without reconfiguring PETSc?

>    In my mind the —prefix should (if used) generally be a path unique
>    to a particular build of PETSc (that can be removed with a single
>    rm) and NOT standard locations like /usr/local where they get mixed
>    up with packages installed in other ways. We could even add a
>    warning :-), that no one will read.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140908/c433afe7/attachment.sig>