On Fri, Jun 23, 2017 at 5:55 PM, Roy Stogner <royst...@ices.utexas.edu> wrote: > > 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".
I agree with that after thinking once more about the "general user". > > (that said, Spack looks cool) > --- > Roy -- Julian Andrej Chair of Automatic Control Faculty of Engineering Kiel University Kaiserstrasse 2 | 24143 Kiel | Germany L: Room F-116 T: +49(0)431 880-6121 F: +49(0)431 880-6278 j...@tf.uni-kiel.de | http://www.control.tf.uni-kiel.de ------------------------------------------------------------------------------ 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
