On Thu, 22 Jun 2017, Julian Andrej 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.
For most of our configuration options, the relevant users' needs are "I need to not spend a lot of time hunting down and reading about and configuring and building a dozen other packages first". This need is already satisfied, even with a fully-featured libMesh, if "yum install libMesh" automatically installs all those features' dependencies too. We'll want "two sizes fit all", IMHO - "libmesh" and "libmesh-complex". (that said, Spack looks cool) --- Roy ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
