On Sat, 17 Nov 2012, Derek Gaston wrote: > So I'm only going to argue for configure in the repo one more time.
For what it's worth, I generally *despise* putting intermediate, generated files in svn repositories. The PECOS svn tree log is littered with entries that are nothing more than roystgnr is svn removing other users' regeneratable files the way Rain Man picks up toothpicks. I count configure in the "stuff to get out of the repo" category, in an environment like PECOS where professional IT people (or Paul or me, at least) are making sure that everyone has access to a tested recent autotools version. But in a publically-available project? Let's make an exception. Until we start auto-tarring nightly releases or doing something similar to give users a minimal-dependencies way to build a recent libMesh, let's leave a pre-built configure in svn. --- Roy ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
