Oddness for PETSc linkage through libMesh

[pbauman]

Martin Luethi complained about having to add PETSc to his LD_LIBRARY_PATH. I always do this anyway, but then @roystgnr reported:

This seems strange. Examining "chkrpath -l grins" I see the path for libmesh; examining "chkrpath -l libmesh_opt.so" I see the path for PETSc. I'd have thought that recursive definition would have been sufficient for the linker to find PETSc when grins is run.

And wait... it is sufficient for me. I use modules on Sysnet but I only use PETSC_DIR (which the linker ignores) on my laptop; there's nothing in LD_LIBRARY_PATH. I wonder what's happening differently on Martin's system.

Soo... what's the deal?