The bigger issue is that devel/trunk is on its way out as far as getting its bugs fixed and it's probably time for the rest of us to move to the week of code branch for doing science.  That is a whole other conversation.

I know this isn't really the appropriate venue for a discussion of enzo issues, but I would like to mention that I'm heading to UCSD momentarily for a couple of days of conversations with Mike and the UCSD Enzo folks regarding the Enzo petascale project (more specifically, the Blue Waters PRAC project).  One of the points of discussion is going to be the next public release of Enzo.  In our conversation yesterday, Mike and I specifically talked about the code fractionation and what to do about it, though we didn't reach any conclusions.  If anybody has any thoughts about this, I encourage you to email me directly before Monday.