As we discussed yesterday, im on board making the next distribution with a configure that has this option enabled, but I thought trunk was going cold turkey??
-Ben On Sep 14, 2012, at 11:52 AM, "Roy Stogner" <royst...@ices.utexas.edu> wrote: > > On Fri, 14 Sep 2012, Kirk, Benjamin (JSC-EG311) wrote: > >> By default the ./configure in trunk does not add the old search paths, >> however this can be re-enabled with >> >> ./configure --enable-legacy-include-paths > > Let's default this to enabled for the next release, to make adjustment > easier? Plus, if you really want to push users into making their code > more random-third-party compatible right now, let's add a configure > option that turns on LIBMESH_REQUIRE_SEPARATE_NAMESPACE. At least in > that case there's been more than a little advance warning. > --- > Roy ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
