Re: [Libmesh-devel] OpenHPC

[Kirk, B. (JSC-EG311) <ben...@na...>]

Thanks for the link!

I really don’t see it as an either/or; both would certainly be welcome and are valuable for their own audiences.

As for the premise of the question, I’m not sure.  Certainly libMesh supports a lot of configure options (too many now?), but a default build compiled against a binary package of PETSc would be pretty easy to do and valuable for someone just getting in to the library.

-Ben


> On Jun 22, 2017, at 2:30 PM, Julian Andrej <ju...@tf...> wrote:
> 
> Isn't libmesh a component which is heavily dependent on the users
> needs? So a "one size fits all" RPM is a bit off.
> 
> In my opinion extending something like [1] (to support more options)
> would be more appropriate. With Spack you can choose whatever
> compiler/MPI/PETSc/Trilinos version or version combination YOU want to
> have.
> 
> [1] https://github.com/LLNL/spack/blob/develop/var/spack/repos/builtin/packages/libmesh/package.py
> 
> On Thu, Jun 22, 2017 at 9:21 PM, John Peterson <jwp...@gm...> wrote: