On Thu, 25 Oct 2012, Paul T. Bauman wrote:
> IMO, it should ship with a configure (built from the bootstrap) and > the bootstrap script (really just autoreconf). configure will > generate the Makefiles and the user doesn't need autotools, but if > user wants to monkey with the build system, they can then bootstrap, > configure, etc. Should be very similar to the current trunk from the > user stand point. For release versions, we ought to be able to upload the output of "make dist", right? That has configure and everything.in pregenerated, yet it ought to still include the .ac and .am files for anyone who wants to monkey with the build system. What do we do about people who want to follow svn, though? I'd vote for our current "check in the results of ./bootstrap" policy, despite the results being slightly more voluminous. The only alternative would seem to be insisting that users work on the "buddy" system, wherein if you can't build autotools yourself you find someone who can to ship you a "make dist" when you need an update... --- Roy ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
