On Wed, 21 Nov 2012, Kirk, Benjamin (JSC-EG311) wrote:

> I'd like to rework the makefile not to include Make.common, and that
> means moving the compile rules into it directly.

Why?  In my experience, when you hand users ten copies of the
same original Makefile (or when you so much as make it easier for them
to copy than to symlink or svn:external a master copy...), you end up
with 4 outdated copies, 4 copies with new (but mutually incompatible)
design changes, and 2 copies outright broken.

> I'd also like to get some feedback on this approach since these
> self-contained examples should be the way people get introduced to
> the library, and I want to set good 'best practices' with the
> Makefile!

Best practices are that you don't copy-and-paste code, no?  Having
"make install" do the copy-and-paste for you doesn't get out of that.
---
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

Reply via email to